Jos,

Too lazy to read whole thread, but I found this in Help...
"If an ON ERROR routine is in effect and a command is attempting to lock the record or file, the ON ERROR routine takes precedence over additional attempts to lock the record or file. The ON ERROR routine is immediately executed. Visual FoxPro does not attempt additional record or file locks and does not display the system message.".

Got an ERROR in effect?

cheers
>><snip>
>>
>>try to clear the keyboard buffer
>>

>>CLEAR TYPEAHEAD
>>IF RLOCK()
>>

>
>No thats not it. This job that the app does is in a loop. It goes through all records in the database and has been running for weeks. The behaviour is the behaviour I want but I am curious as to why the RLOCK() returns .F. and continues instead of waiting with the "Attempting lock ..." message.
>
>I feel as if its one of the other SET commands in the app or the way the app runs from a form which somehow overrides the default REPROCESS behaviour?