Hi Kevin,
Something's wrong with you scenario. AFAIK, RLOCK() doesn't trigger foxpro error but returns .F. when it fails.
>After years, I find that I may not understand record locking as well as I thought!
>
>Let's say I have a SET REPROCESS TO 10 SECONDS
>
>And then I try to do an RLOCK() on a record that a user wants to edit.
>
>Let's say the RLOCK() fails after 10 seconds...control goes to my error handler.
>
>In the error handler, I trap error 108 (record is in use)...the 'problem' is that in the error handler, I want to be able to present the user with a messagebox and ask them if they want to retry (so they can go find out who has the record locked, then respond to the message). However, it appears that RETRY doesn't try for another 10 seconds to lock. Is that correct?
>
>TIA,
>Kevin
--sb--