Record locking

[Brian]

I have a continuous form containing a text box bound to a field that
represents the record sequence, and when the user wants to manually rearrange
the records, he simply enters the sequence number in the box (this is a
delivery stop sequence for a home-delivery business).

I simply run a query in Form_BeforeUpdate to renumber the sequence field for
all affected records. I have taken great care to ensure that the current
record is excluded by the WHERE clause of my SQL statement.

I have record-locking set to Edited Record as both the DB default & on the
form, but I am getting lock violations.

Is it because I am trying to do it in Before_Update? Even so, why should I
get lock violations on records other than the current record?

 

[Alex Dybenko]

Hi,
if you are using page locking - then not only edited record is locked, and
this could be reason you get error message. You can try then to use form's
AfterUpdate event, but personally I would set page locking to no locks

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com

 

[Brian]

Thank you.

I had forgotten that "Edited Record" does not mean "Edited Record" - it
means "all the records on the same page as the Edited Record".

I just turned off record locking for the form. One follow-up question, though:

How does form-level record locking interact with or relate to DB-level
(Options -> Advanced) record locking? Does the general one override the
form-level one, is it a default, or is there a more complex interaction?

 

[Alex Dybenko]

Hi,
I think DB-level is default one, and form level override it

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com