>>Then how can you explain the RLOCK failure? Is it possible that the record/file is locked in another data session? Are you able to reproduce the problem on a new DBC with only two tables? Could you zip it up and send to my e-mail along with the repro code?
>>
>
>I have stepped through the code again with the debugger and it is not the RLOCK that is failing. It appears to be the UNLOCK that fails. When I hit the UNLOCK command, I go to the ON ERROR routine, but VFP does not throw up an error. The code just continues on as if all is ok until I return from the RI_INSERT code then I get the "trigger failed" error.
>
>As I have stated before, this only happens on a handful of my tables and when I step through the code with the debugger, I do NOT get "trigger failed". I only get "trigger failed" when I let the code run without stopping. Could this be a timing issue?

Hi Debra,

We can continue guessing and not find what causes the behavior until the issue is properly investigated. In order to do this, a repro is required. Could you provide a repro scenario for us? You don't need to make it public if you don't want to.

Thanks,
Aleksey.