Hi Michiel,

First, I am no Ed Pikman. . .

But I did want to offer some comment:

1) You *can* find out if a record is locked BY THE CURRENT USER using the ISRLOCKED() function. Apparently it will only return .T. in the case that the session issuing the ISRLOCKED() function is the same one that has the lock on a record. Otherwise it will return .F..

I use the word 'apparently' because this is less than clear in the Help, but has been stated many times by acknowledged VFP pros.

In addition, I don't really see a problem with issuing RLCOK() many times in the same session for the same record, though I would say it mightbe indicative of sloppy code.

Cheers,

Jim N

>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?