By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,635 Members | 917 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,635 IT Pros & Developers. It's quick & easy.

Write conflict (Record locking)

P: n/a
Dear reader,

In case I work with two Forms and using the same Table but with other fields
in the Forms, I have the following experience.

After I change in one of the two Forms a field I can't move to another
record in the other form because of a record locking problem.

How can I avoid the popup window witch telling me:

"The record has been changed by another user since you started editing it".

The setting under "Tools", "Advaced" under default records locking is "no
locks" and "Open databases using record-level locking" is disabled.

Thanks for any help.

Kind regards,


Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Of course, that other user is the other form.

The solution is simple:

When formA launches formB, you do two things:

Make formB model (in the other tab settings), and then in your code...make
sure the first form writes out all data to disk..

docmd.Openform "formB",,,"id = " &

The user will then be forced to close formB "before" returning back to
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.