Hi,
I have an Access 97 database containing two tables: a linked table, and a local Access table. The link points to an SQL Server 2000 table with 12000+ records. These two tables must stay more or less in sync, so I run a "Find Unmatched" query regularly against the local Access table, so I can keep it updated.
Here's the problem, the "Find unmatched" query always says that 95 records are unmatched, when in fact, they're matched -- they exist in both tables.
To troubleshoot this problem, I made an exact copy of my big SQL table using SELECT ... INTO, and placed it locally in my Access database. Then I ran that same "Find Unmatched" query against that, and it worked, it says that there are 0 unmatched rows, which is correct.
Did anyone encounter this problem before? It seems to be a bug with Linked Tables in Access or a bug in SQL server, and it's a pretty serious one. It's not the first time that I see this happening.
If anyone has an idea please let me know,
Nader
I have an Access 97 database containing two tables: a linked table, and a local Access table. The link points to an SQL Server 2000 table with 12000+ records. These two tables must stay more or less in sync, so I run a "Find Unmatched" query regularly against the local Access table, so I can keep it updated.
Here's the problem, the "Find unmatched" query always says that 95 records are unmatched, when in fact, they're matched -- they exist in both tables.
To troubleshoot this problem, I made an exact copy of my big SQL table using SELECT ... INTO, and placed it locally in my Access database. Then I ran that same "Find Unmatched" query against that, and it worked, it says that there are 0 unmatched rows, which is correct.
Did anyone encounter this problem before? It seems to be a bug with Linked Tables in Access or a bug in SQL server, and it's a pretty serious one. It's not the first time that I see this happening.
If anyone has an idea please let me know,
Nader
Last edited: