>I would be interested in knowing how the RLOCK() is used to clear the locks. I've worked with a few systems (FPD,VFP, Pick Basic, etc) that utilize similiar "soft" locking techniques and I often find myself spending more time clearing these locks because of machine reboots, code crashing, or developers not adhering to established standards (ie. not using the modularized locking procedures, or not adding the extra field(s) necessary to track the locks).
>

PMJI
For some apps, a "user" lock saves physically locking the master record. To work around the crash problem, where the user ID is left in the table, I have a routine that puts the userID and a day/hour signature in the user id field (2 characters can represent day/hour) - The soft-locking simply ignores user locks that are too old. Voila! no maintenance.
HTH