We recently Migrated an access database onto a SQL server. Upon completion we began testing the database using the front end access database we had (Our previous setup involved two access files, one for front end and one for back end.) We almost immediately received the error.
the Microsoft access database engine stopped the process because you and another user are attempting to change the same data at the same time.
Now we do have multiple people working on these front ends but at the time of receiving this message, I'm the only person accessing the data. My general process for testing it has been to insert the data using the form. then attempt to delete the data. I know for a fact the data is making it to the table and I know for a fact I'm the only one viewing or attempting to edit this information we used an ODBC connection to attach SQL server to the front end. Any suggestions or help is greatly appreciated, I will be monitoring this thread heavily so Expect any questions you ask me to be answered relatively fast.
In this article, you will find that the error can be caused by the bit data type:
This problem occurs if fields with a bit data type in the SQL Server-based database have been left blank. Microsoft Access interprets blank fields as fields that contain Null values, and the Jet database engine does not release them. As a result, the records remain locked and are not available for deletion.
Note that you must always have a primary key or unique key to update data from SQL Server.
This answer solved my instance of the problem. I am using ODBC to communicate with MySQL.
The support article for this is at: support.microsoft.com/en-us/kb/318882 -- not sure if that is what you originally linked to or not.
For me, the problem was caused by a bit field with no default value. Adding a default value to the bit field solved it.