Best practice in locking records

[TallGuyinIT]

Can someone help me with the best practice in locking a record while updating? I am trying to update an existing program that occasionally does not update the record. I have looked at other existing programs and the Microsoft knowledge base. There are several options. I am trying to determine which one is best practice, or is there even a better way.

Option 1 (existing code)
SET REPROCESS TO 0
SEEK (locate the record)
IF RLOCK()
*Code to update record
UNLOCK
ENDIF

Option 2 (other programs on our system)
SET REPROCESS TO 0
SEEK (locate the record)
DO WHILE RLOCK()
ENDDO
*Code to update record
UNLOCK

Option 3 (microsoft)
SET REPROCESS TO 0
SEEK (locate the record)
?RLOCK()
*Code to update record
UNLOCK

Any opinions or other options?

 

[Mike Lewis]

Surely, the answer depends on the extent to which users are prepared to wait for the lock, and the action you want to take if another process fails to release a lock in a reasonable time.

Mike




__________________________________
Mike Lewis (Edinburgh, Scotland)

My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)

 

[alvechurchdata]

is there even a better way.

Can you use buffered data and just let TABLEUPDATE handle the locking for you?

Geoff Franklin

http://www.alvechurchdata.co.uk