Posting for an end user at a remote site.
There are two users of an application, each user their own laptop.
User1 receives "Violation of PRIMARY KEY constraint xxxxxxxxxxxxxxxxxxxx. Cannot insert duplicate key in object xxxxxxxxxxxxxxxx" on their laptop
User2 does not receive this error for the same record on their laptop.
If User1 logs into the laptop of User2, they receive the same error.
If User2 logs into the laptop of User1, they receive the same error.
You would expect it to fail for both users on both machines.
This MS Access 2003 and SQL database application has been in use for years on a daily basis.
Six months ago the users machines were upgraded to Win10 / Office 365, and MS Access 2003 has been AppV virtualised. Its been running successfully in this format since then.
Any thoughts on this error going off the above synopsis?
No access to logs, nor the data structure/data at this time.
I am not the developer of this database, I know nothing about it, except that the end user requires Access 2003 to use it and it has a SQL back end.