>Hello Edward,
>
>>If TABLEUPDATE() returns .F. it already gives you signal that record was not updated, i.e. additional error trap is not a necessity, though it still should be here, because sometimes you might get error message.
>
>Well we tested alot and it seems that if you put a RLOCK() on a record you can put a RLOCK() on that record without any error messages (with the same user that is). So in other words you can never know if the record is locked or not if the current application put a RLOCK() on a record.
>
>Is this correct?

Firstly, it's not the best app setting when RLOCK() will be applied to the same record from the same workstation. Theoretically, you should get error message in this case if you use private DS (i didn't test it specifically). Basically, if you consider own workstation app flow, you have enough tools to prevent locking of the same record twice. For example, each form locking a record can keep current record number as property or add this number to some app collection and another form may first check this number there and make a decision.