>>Hi All
>>
>>I have a weird thing going on with RLOCK(). I have an app which starts at record 1 of a file and attempts to lock it using RLOCK(). If it returns .T. I do something with the record. All is fine.
>>
>>If I run another instance of the same app it also starts at the first record and attempts RLOCK(). It returns .F. because the first instance above has a lock on record 1 and so it moves on to record 2.
>>
>>This all works fine.
>>
>>However I do *not* have a SET REPROCESS command anywhere in my app and no REPROCESS setting in the config.fpw. The help says the second app should go into an continous wait state whilst attempting to lock record 1 because the default value for SET REPROCESS is 0. But this does not happen! The second instance of the app attempts the RLOCK(), it returns .F., and it continues to the second record.
>>
>>Why?
>>
>>I cannot make this same behaviour happen if I create a simple exe project to emulate the above. The simple exe test goes into a "wait or press Esc situation" as expected by the help documentation. I assume therefore that it is something unique to the main application but what could be the reason?
>
>try with -1 or -2.


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.