OK, I'm going to get horribly beaten for this one, but perhaps this thread could finally make me change my error handling ways ...
I'm not a big fan of blanket error handling code - I think that it makes errors very difficult to find in testing.
The way that I do error handling is like this.
1) Option Explicit in every file - probably the most important thing.
2) Check every return value from every function, and do something sane
3) Use On Error Resume Next and If Err around portions of code that can raise errors. Handle the errors at the point they occur, if possible.
4) If the error is disastrous, bring up a dialog box telling the user and exit immediately. Do NOT try to save state, as you have no idea what the state is.
This is just a basic framework of my error handling. OK guys, open season. Shoot me down.
Chaz