Access database engine stopped the process because you and another user are attempting to change the same data

sql-server-2008 ms-access ms-access-2010
ChettDM picture ChettDM · Mar 12, 2013 · Viewed 38.6k times · Source

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.

Answer

Fionnuala picture Fionnuala · Mar 12, 2013

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.

Related questions

How do I create a passthrough query in access using a DSN-less connection?

I'm using DSN-less connections to my SQL Server in an Access database. However, whenever I try to write a "Pass-Through" query and run it, a dialog box pops up asking for the DSN.

Read More
Editing Record issues in Access / SQL (Write Conflict)

a problem has come up after a SQL DB I used was migrated to a new server. Now when trying to edit a record in Access (form or table), it says: WRITE CONFLICT: This record has been changed by another …

Read More
Using output parameter from SQL Server stored procedure in Access

I am attempting to get an output variable (the new identity column) from a stored procedure in SQL Server 2008 after executing the procedure from Access 2013 VBA. I don't fully understand all the adodb stuff, and I've tried a number of …

Read More