Hi David,

You're right, but consider this situation: we have an application, called XFormDBF. This application has its own Error Handler. This application allows to use UDFs. One of my UDFs called OpenTble and it uses ON ERROR mechanism to check, if table could be opened. Now, this is just ignored and I see an Error from this application instead of trapping this problem by myself.

>Nadya,
>
>I'm sorry, but there's nothing unfortunate about an object being fully in control of any errors that occur within the code of the object itself. That is the way things should be in a good object-oriented language.
>
>>As you already figured out, there is no way and that's unfortunate. I was caught by this behavior couple of times... I'm not sure, we can wish about it for Toledo, because adding ability to switch will break the existing code...