My backend is an SQL server and the front end uses linked tables in access. everything works fine except the following situation.
If a user makes a change on a form, and then changes it back, then tries to move to a different record (or anything that causes an update I think) I get a write conflict error with the options to copy or drop. You can choose 'drop' and nothing is lost - because nothing was done really.
Think of checking a check box, then unchecking it and moving away.
I've error trapped this in the OnError event, but suppose the user clicks a "goto next record" button. Even if I trap the write conflict error it's followed by a "Can't go to the specified record" error.
My nav buttons are coded so that if you're on the first record the "previous" button is disabled so that normally handles the type of error. But that is moot when the write conflict messes it up.
Any ideas?
(Thus far I've just told my users not to do that lol, but I'd like a better solution)
EDIT: In addition, I've tried adding timestamp fields as recommended by several people to fix the write conflict. This results in a 7776 error which as far as I can tell is unfixable