I'd like to know more about what kinds of errors your routine isn't catching. Have you been reading the other thread on error handling today? David Frankenbach has clear thoughts on error handling. He reminded me that ON ERROR is superceded by an object's error event...Do you use the error events? That might be why your clear events isn't firing.

Also, IMO, just having a MESSAGE() call in an error routine isn't satisfactory. For example, if you have an error due to an primary key uniqueness violation, you have to do something different than for a badly named controlsource.

I'm still working on application-wide error handling. At this point--and it's just my preference--I'd rather find the errors and fix 'em. That's just where I am in the development (plus, I don't use a framework). However, since weird stuff happens, I know I have to include logging and graceful exits. So, I read everything people post on error handling and make lots of notes :-)

P.S. My favorite method in my app object is ClearObjects() :-)
P.P.S. I think (most) every mortal feels like they should redesign their app object. I know I do!

>I do have an application object but it doesn't handle EXE terminations.
...snip
>What properties and methods does your favourite application object have? Maybe I should redesign my application object?