>Hi
>
>I'm working in a system where there is an intermittent problem with locked records stopping jobs from running. As the users only sees a message stating Trying to lock record etc.....
>
>I want to pass this error to my own error handler to display the record that cannot be locked.
>
>I set reprocess to 1 and in the error handler display the key of the current(locked record) and then retry.
>
>My question is. Is this bad from a performance view or are there any other ways to handle this. I should add I have little control over the data environment due to the nature of the overall system.
>
>Thanks
>
>Nick Mason

Since you're doing a RETRY rather than a RESUME after displaying the message, I'm assuming that the user just keeps seeing your message up there instead of the VFP message. Why is this preferable? I would say performance isn't an issue at this point because the record is locked and the second user can't do anything with it anyway.

There may be some better ways to handle this situation, but I would need more info to know what to recommend. It seems that if it's a common occurance for running jobs to get this message because of other things going on, you should take steps to avoid the conflicts sooner. For example, you may want to open files needed by the job EXCLUSIVE so that other users don't interfere.