Of course it is not real code, it is a simple example of a way to generate the error. I want to trap the error. What I do not want is a dialog box poping up and blocking the operation of an unattended process. ON ERROR does not fire unless a user intervenes and responds to the dialog.

I do not know the exact code that generates the error, if I did, I could fix the problem. The problem is very rare, and I am trying to find its cause.

>>Is there a way to disable the table open dialog that pops up on error like the one generated by this code?
>>

>>SELECT 0
>>SKIP
>>

>
>Is that the real code? If so, I'd suggest that you shouldn't disable it, but fix it. SELECT 0 is, by definition, selecting an unused area. To do a skip is flat wrong.
>
>Otherwise, select by alias and not area number, to be safe. And, if you can't be sure the alias is in use, check USED() first.
>
>While I think this is a case where the error message is helpful and shouldn't be disabled, if you must, then you can do it with ON ERROR or with the error method (depending on context).