Try adding a field called Time_Stamp to the SQL Server data table and set it's field type as TIMESTAMP. (Note: You may have to delete and re-link the table.)
Also make sure you have a field defined as int on SQL Server (similar to an autonumber field in MSAccess) and set the identity = Yes. Don't forget to set up a primary key if one doesn't exist (ie. the field you don't want duplicates on.)
You can also just try refreshing your linked tables. Sometimes I would try re-creating the ODBC DSN. You also want to make sure that ALL users who utilize the application have the EXACT same ODBC DSN name on everyone's computer.
I can't recall if updating the MDAC on the machine(s) had anything to do with this problem or not (I experienced it several times years ago and troubleshot different reasons.) There may also have been some kind of service pack for it if it was ODBC related. You'll want to research this more.
You can also try just a "Refresh" or even re-indexing on the SQL Server table itself in the Enterprise Manager.
Last edited by pkstormy; 09-21-09 at 23:59.
Expert Database Programming
MSAccess since 1.0, SQL Server since 6.5, Visual Basic (5.0, 6.0)