You could still use the same logic. Just test the success of RLOCK() to decide if you will allow the user to edit the record. Any time the RLOCK fails, you know that someone else is editing the record, and it should be readonly for this user, or you can just allow the user to go to the next record.

>Thanx for the suggestion but I am was trying to have the system gererate a POPUP when a record was in use. In such a circumstance, the users could then skip over the record now, make changes to it later, but look at it now, which would reduce conflicts.
>
>I have given up on this logic for now.
>
>Thanx anyway, I do appreciate the response.
>
>>>If a table has OPTIMISTIC ROW BUFFERING how can the system check if a record is open (i.e. being displayed on someonese screen but not necessarily being changed)?
>>>
>>>Unless someone changes data, the record is not locked so RLOCK() does not help.
>>>
>>>I am looking for something like USED() but relating to records (not tables.)
>>
>>You could RLOCK the record explicitly everywhere, so after one user has RLOCKed it, the other user tries, and can't.