I am attempting to link two tables from SQL server to an access application. Both contain the same column names and the same fields as concatenated primary key but the tables are named differently, have different values and used differently. When these ta
bles are linked in access, one of the tables changes to a single primary key. When this table is opened, you see many duplicates (of what was the concatenated primary key) but the count of records is still equal to SQL Server. When I query in Access for d
uplicates, no results are returned. I drop the table and re-link it, but it still shows a single key. How can I get Access to accept the true table schema?
"bbitzer" <anonymous@.discussions.microsoft.com> wrote in message
news:0219C2D0-5ADB-48E7-86D0-EAC93D9D5422@.microsoft.com...
> I am attempting to link two tables from SQL server to an access
application. Both contain the same column names and the same fields as
concatenated primary key but the tables are named differently, have
different values and used differently. When these tables are linked in
access, one of the tables changes to a single primary key. When this table
is opened, you see many duplicates (of what was the concatenated primary
key) but the count of records is still equal to SQL Server. When I query in
Access for duplicates, no results are returned. I drop the table and re-link
it, but it still shows a single key. How can I get Access to accept the true
table schema?<
On the surface it sounds like a bug... make sure you update your client with
the latest MDAC and Jet updates. Also, on the tables you mention on SQL
Server, be sure that you have added an additional column of data type
timestamp.
Steve
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment