[X]My Assistant

[isladogs]

That doesn't sound like the cause to me but as I said, I haven't looked at your code.
You can force data saves E.g

CODE

If Me.Dirty Then Me.Dirty =False

Also check recordsets are closed after use (possibly irrelevant but good practice anyway) etc

[KarinG]

Hi Colin.
I had "If Me.Dirty Then Me.Dirty = False" already in there, but I added a few more at key spots. I also double checked that I was closing all recordsets. I am still getting the same error.
Karin

[isladogs]

It shouldn't be necessary to keep reusing that line.
I'm about to logoff so won't be reviewing your lengthy code tonight. Hopefully someone else will.
In the meantime have you tried stepping through the code to check what triggers the conflict?

Perhaps you need to post a stripped down version of your app to illustrate the issue

[KarinG]

It is the Me.Requery that triggers the error. I will try removing some code so I can post a condensed version of what is causing the error.

[KarinG]

I found the statement causing the issue.

CODE

Forms![frmVendorMain]![optGroupStatus] = 2

It doesn't like it when I make a change on the main form. I can make changes on the tabs but not the main area. I tried putting the Me.Dirty = False right after I make the edit on the main form but it still gives a write conflict error.

To get around it I had to update the information via a recordset instead of updating the form.
This post has been edited by KarinG: Oct 9 2019, 12:30 PM

[theDBguy]

Hi. Glad to hear you got it sorted out. Good luck with your project.