>Our office is working on an error handler. But unlike others that allow a full cancel of the application, or ignore, we need a different control approach.
>
>Our primary application may have multiple other forms loaded that may not be related to the one form that caused an error. We want to kill anything related to that single form instance back to the initial READ EVENTS. Problem is that this form may call up a modal dialog. The call stack does show the full hierarchy from the
>

>READ EVENTS
>  Form5
>    Btn.Click()
>      NewModalForm
>        ModalBtn.Click()   -- error
>

>
>What methodology can we use to return control back to the read events without requiring the entire appliation to be closed. One kink though, We may have multiple instances of "form5" and the other instances are not affected.
>
>Any help would be appreciated.
>Thanks

You should read the article on error handling at www.stonefield.com