>>>Which would be obvious if i wanted to put error routines on every one of 300+
>>>controls, but i'm trying to use a global On Error routine.
>>
>>Sarek points Michael in the general direction of using subclassed controls so that he doesn't have to put the error routine on every one of 300 controls. He then waves at hand-hacking the .SCX, to head off the next objection...
>
>Live long and prosper, and then take a look at Doug Hennig's error handler as
>a start for the global error handler. Quark points out that controls should
>handle the errors that they understand, but points out that it isn't the
>responsibility of each control to deal with all possible errors! They don't
>get paid enough!

I haven't read Doug's yet, but Mac Rubel gave a presentation to our user group explaining his philosophy: each control handled the errors it knew about, and passed them up the inheritance hierarchy if it didn't know what to do. When you hit the base class, you started walking up the containership hierarchy. If that didn't work, only then did you hit the global error handler, which just logged the error and shut down, because you were screwed. :-)