September 17, 2001 at 7:39 am
I have an application with a Access front end. On one of the forms users are getting a consistent write conflict. I have been unable to figure out why it is happening with that form. Could someone let me know why this could be happening.
September 17, 2001 at 8:43 am
Not much to go on. By write conflict do you mean an optimistic locking error, someone else has modified the record? Could you post some code and detailed error messages?
Andy
September 20, 2001 at 2:42 pm
Here's what I'm doing. After the user clicks a button I run code that updates all the necessary fields using Update statements. Once the Updates are complete I have code that refreshes the form. After the refresh I receive Write Conflict. Another has updated the same information. Then I can either drop the changes or copy them to the clipboard.
September 20, 2001 at 3:09 pm
This sometimes occurs with bound controls. Sorry I'm not so much of an Access guy, but I've seen this with VB/FoxPro. We would store the data in a variable which was assigned to the form rather than binding the form to the data in the recordset.
Steve Jones
September 22, 2001 at 11:38 am
You will also see this if you have an trigger that is modifying the same rows you just modified (to set a datestamp is a good example).
Andy
October 8, 2001 at 4:03 am
I had the same problem with a few of our ms access programs.
The fix is to open all sqwl server tables used by access in design and assign a default value of 0 (zero) in all bit fields.
Afterwards you must update records with null value to 0 or 1!
I hope this one is solving your problem
Jan Peder Arnesen
Jan Peder Arnesen
October 8, 2001 at 4:08 am
A full solution for the problem can be found at this article from microsoft!
Jan Peder Arnesen
Jan Peder Arnesen
October 8, 2001 at 7:35 am
Thanks for the follow up Jan - I'm sure future readers will appreciate it!
Andy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply