Hi Erik.

>What I have tried to do is trap for the error and allow the user to cancel or retry. Since I think the record is only being locked for a split second, I thought this strategy would work nicely. Unfortunately though, issuing a RETRY from the error routine produces a VFP error (not trappable) that says something like "Mismatched Pushjmp/Popjmp call" and the app quickly exits.

I'd have thought RETRY would work too, but can sort of see that this is a different case than the normal record locking problem. You might instead tell the user you have to close the form because of a resource contention (not those exact words <g>) and then do so. That way, they'd control reopening the form. Alternatively, you could have a timer do it automatically, but that raises issues like what happens if the error occurs again.

Doug