Originally Posted by
pkstormy
If possible, I would create a new ODBC DSN to link the tables and then link them into a new accdb file. Make sure when linking the tables that you check the box which says "Save Password".
Also keep in mind that if there is another accdb which links the same tables but uses a different ODBC Name, this can cause symptoms where it works for one user, then doesn't, then after refreshing the linked tables it works again for that user but then doesn't work for another user (even if the ODBC Name is spelled or capitolized slightly different). Remember that anyone which links to those tables must have the exact same ODBC DSN name or you'll get mixed errors which can drive you crazy.
This also assumes that you have the tables setup correctly with an identity field which can often cause issues if there isn't an identity type field in the table (with it set to auto-increment). Also try adding in a 'TimeStamp' defined field into the table. Some SQL Server db tables don't like being updated in certain environments if there isn't a timestamp defined field in the table. After I added a timestamp type field to the table, issues such as you described went away.