>>>
>>>
>>>Hi Fabio, Cetin, Gregory. I do not have a REPROCESS command anywhere in my app and yet I do not get a "Waiting for lock...Esc to cancel" message on an RLOCK on a record which is locked in the first app instance. It just returns .F. but should actually create the wait message. It behaves as if I had REPROCESS set to 1 ie. one attempt. But the docs say the default value is 0.
>>
>>Jos, i try it with two machines now, and it stop for the ESC.
>>
>>Debug it:
>>

>>WAIT WINDOW TRANSFORM(SET("REPROCESS"))+CHR(13)+TRANSFORM(SYS(3051));
>>+CHR(13)+TRAN(RECCOUNT())+CHR(13)+TRAN(RECNO())
>>* 0 , 333 ...
>>RLOCK()
>>

>
>Fabio, in my simple test app I get the documented behaviour. In my actual live app the debug shows:
>
>REPROCESS=0
>SYS(3051)=333
>RECNO()=15197
>
>for both instances of my app. ie both apps tried to get the same record number, 15197. The first one got it and the second got an RLOCK() = .F. and moved onto the next record automatically without waiting for "Attempting to lock ..." message. REPROCESS=0 but behaves as if REPROCESS=1

Jos,
I couldn't understand the part "and moved onto the next record automatically". Why would it move to the next record when rlock() returns .F.
Cetin