"Write Conflict"? Why?

D

Dennis

In Acces 2003, I've designed a popup form that allows the user to specify
certain filter criteria. I do an ADO lookup based on those criteria, and if
records are found, I set the main form's "Me.Recordset" = the recordset I
found via lookup and close the popup. There is a subform in another tab,
Linked by a key value in the main bound form's associated table.

When the user attempts to change a field and clicks to post the change, the
following message is displayed:

-------------
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 allow you to.. (etc, etc, etc)
----------------

The options provided are:

Save Record, Copy To Clipboard, Drop Changes

However, NO OTHER USER has the record open at that time. Further, if the
user clicks "Save Record," they're not allowed to. The same dialog box just
keeps opening over and over again. Can anyone shed some light into what I did
wrong from a coding standpoint? (I'm not using QBF, since I really don't know
how to use that functionality properly.)

Any insight would be appreciated.
 
A

Arvin Meyer [MVP]

My guess is that the subform records are the same as the main form's and the
"other user" is you. You will need to get rid of the subform to solve the
problem. To make sure, copy the form to a new name, then delete the subform
and see if that helps.
 
D

Dennis

The subform's records come from a different table. The table relationship is
one-to-many. (There is one "demographic" record and multiple "status" records
for each person.)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

sqlite-odbc write conflict 2
Write Conflict 8
write conflict 2
write conflict 4
Write Conflict 2
Write Conflict warning 3
write conflict 4
Locing records i nmulti user 6

Top