Connecting Tech Pros Worldwide Help | Site Map

Write conflict (Record locking)

Simon
Guest
 
Posts: n/a
#1: Nov 13 '05
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,

Simon



Albert D. Kallal
Guest
 
Posts: n/a
#2: Nov 13 '05

re: Write conflict (Record locking)


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..

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

The user will then be forced to close formB "before" returning back to
formA.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn


Closed Thread