>Haha...well, if a global error handler was in place, at least the error would be handled and the user wouldn't have experienced a crash...some situations demand that the program gets out to the user by a deadline...and object-specific error handling is not always a priority.
>
>Are you suggesting a global error handler is not be better than sitting back and waiting until the program crashes on the user in those spots where you forgot to program error handling code?
>
>Joe
>


Not at all. As I recall, there wasn't an error handler to begin with and someone said "The global error handler should catch it". I simply pointed out that there is a more OOP way. BTW, if you read the article I suggested (www.stonefield.com), you'll find that errors are also trapped at the parent class level, thus handling the situation where you need to get the program out. IF a particular object does not have its own error code, the error handler travesl up the parent class chain. If it still doesn't find anything, it starts looking at the form, and traveling up its parent class chain. If it still doesn't find anything, the global handler is called.