Write Conflict Error in Access 2000

[soloprogrammer]

I just recently converted an Access 97 application to Access 2000 with a SQL server backend database.

Here’s the issue: The users are getting the following error: “Write Conflict—The record has been changed by another user since you started editing it. If you save the record, you will overwrite the other user made”-- with the buttons Save Record (which is grayed out and unavailable), Copy to Clipboard or Drop Changes. They get this error when they try to update certain fields in the record. I notice if they create a new manifest (new record) and copy the data from an existing manifest, they DO NOT get the error for these fields. But if they create a new manifest (new record) with user input data, they do get the Write Conflict error.

I set up a test database in SQL Server and I get the same error. I know I am the only user in the application. So the write conflict error just doesn’t make sense to me.

The datatypes for these fields with the problem are defined in Access as TEXT and in SQL Server as VARCHAR.

Also the application was originally written in DAO.

Any suggestions would be great!

Thanks in Advance

 

[betsyr]

I had this problem too with a one-user database. It turned out to be because I was making changes to one table at multiple times without saving my changes to the table in between. I think I was updating a table with a recordset using code, and when the form closed it was also trying to update the table. What I ended up doing to fix it was walking through all my code and figuring out when I was writing to each table. I had to commit my changes before making another change.

I hope that makes sense and helps somewhat!

 

[soloprogrammer]

Thank you. I'll try that. That is probably what the cause is. THANKS!

 

[soloprogrammer]

I tried doing this through ADO with a commitTrans. It appears to update with no errors. But when I go to a different record and then back to the original record, the changes are not there.

I opened the table through Access and tried to make the change to the field. When I click off of the record, I get the same Write Conflict Error--and this is through the TABLE not the form.

Do you think it could be some kind of locking issue with the SQL Server table backend?

 

[soloprogrammer]

If anyone else is having this problem, I did find the answer. It was the SQL Server. The datatype BIT was the problem. Here's a link to the solution: http://support.microsoft.com/support/kb/articles/Q280/7/30.ASP

 

[softpro]

Thanks

Hi Soloprogrammer,

Thanks for the information. After I resolved the SQL Server bit nulll problem, I am okay now !

Thanks a bunch !