Write Conflict in subform

[RayMilhon]

I have a Database I designed with SQL Server Back end and Access 2010 Front End. The front end is installed on 4 computers in our company. 3 of the 4 users are having no issues, however 1 is having a problem I haven't been able to figure out.



I have a Data Entry form that is attached to the primary table in the DB. There is a subform for entering comments.

The table for the subform joins to the primary form by the PersonID Field in both tables. The Comment table includes Fields for the Actual Comment, the date of the comment and the CommentID.

the user with the issue is able to enter a comment but if they go back later to edit it they get the following Error

Write Conflict

This record has been changed by another user since you started editing it. If you save the record, you will overwrite the changes the other user made.

Copying the changes to the clipboard will let you look at the values the other user entered, and then paste your changes back in if you decide to make changes.

It includes the 3 Command buttons

Save Record - Grayed
Copy to Clipboard - Enabled
Drop Changes - enabled

It doesn't Matter if anyone else is in the DB or not She gets it everytime she tries to edit any comment. Nobody else gets it. I've checked everything I can think of everything looks fine. Any help is appreciated.

[HillChris7714]

It sounds like something in the accdb file is updating the record while the form is open and it's getting confused. That's kind of a vague answer, but if you're sure nobody else is in the file, it's totally reasonable to assume the accdb is "confusing" itself.

It's not exactly an easy problem to troubleshoot, but... last time I saw this message, I had a FormA that opened FormB, an action on FormB updated the record that FormA is based on. So, when I went back to FormA, I got that message that "someone else" updated the record. Of course, by "someone else," Access is referring to "Another form."

[ItsMe]

As HillChris mentioned, you get this error when you update an Access table via two different forms. The forms can be on one computer or the forms can be on separate computer. I do not know if I would expect to see this message while using SQL Server. What is really intriguing is that other users are not experiencing it and you are apparently using a form/subform combination.

If there are no other form's open on this user's computer, I would suspect corruption. Maybe the subform control is corrupt or maybe one of the form's is corrupt.

[John_G]

Did you reboot the computer with the problem? It could be that there is an MS Access process running, but which you can't see because there is no icon for it. This is usually cause by some sort of abnormal termination of MS Access.

Might this user be opening two copies if the database at the same time, perhaps so that they could easily switch between two views of it?

[rpeare]

have you tried using unbound controls for data entry, this would only touch your data when you recall, add, or update a record instead of keeping a record open indefinitely.

[RayMilhon]

Each Form is linked to different tables. There is a customer table which is what the main form is based on and a Comments table which is what the subform is based on. There is a link between the 2 tables on CustomerID. Like I said in the original post 3 of 4 work perfectly. Had the user reboot the machine didn't help. I verified that there is only 1 copy of Access running. I don't see how using unbound controls would help when it works fine as is on 3 out of 4 computers.

[RayMilhon]

Ok just replaced the existing front end with one that I verified was working on another computer. Still get the same message.

[ItsMe]

Ok just replaced the existing front end with one that I verified was working on another computer. Still get the same message.

Sounds like that user is doing something unique. Are you using the same SQL drivers on each machine?

[RayMilhon]

Yes made sure they were all the same when installed the DB

[ItsMe]

It would be nice to fully understand what the heck is going on. You may have to settle for using an on exit or lost focus event handler to save and commit the record to the table.

EDIT: I had a lapse of reason and remembered that my previous suggestion will not work.

You might try placing the following code in each control that may receive an edit. You will want to do this on the actual subform object and the main form object. In other words on each of the form's and add code to their respective module.

The following code in each control's AfterUpdate event should remedy the symptom.

If Me.Dirty Then
    Me.Dirty = False
End If

[RayMilhon]

Added the If me.dirty then me.dirty = False to the after update event of the control giving the problem. Now it occurs on every machine. Took the If me.dirty statement out and it still occurs on every machine.

[ItsMe]

You will have to isolate the problem. This may sound obvious, but your last post indicates you are not troubleshooting in a "Control Environment".