>Anytime I use an RLOCK(), I followup immediately after my update with an UNLOCK. The only thing I can think of is an inherent record-lock by Foxpro during a browse or do-while-loop. I've inserted a routine that UNLOCKs all files that I'm using in a given routine, regardless of whether I issued a LOCK or not. I'm waiting for feedback from my clients. If you think I'm missing the boat on this one, or if there's any other way by using brute force to avoid the 'attempting to lock', please let me know.
>
>Thanks again for your help.
>
>Chaim

Chaim,

You still haven't said exactly where in the process the "Attempting to lock" message shows up and exactly what the code is doing, and what other processes may be running at the same time. Or does this happen in several places?

There's no way we can give good advice without knowing what is happening in the code.