>Steve (and everybody else who answered)...
>
>Thanks for responding. I agree that the concept of an RLOCKS table makes sense - however, the one issue (which you mentioned at the end) is what to do if someone locks a record, and then loses their connection, has some other type of abend, etc.
>
>I've actually posed a lock table to some of my peers in our company, and their response was the maintenance issue of having to 'clear' a lock in that case. Seems to me that a properly constructed app should minimize those instances, but I am getting resistance from those who think that even having to clear out an entry once a week is too often.
>
>Thanks,

Kevin,
I don't see the issue your co-wrokers are raising. You can create an SP that clears old locks and schedule it using SQL Agent. It could run nightly without any effort put forth by anyone beyond the initial creation.

We do that here for our Oracle database.