Quote Originally Posted by Paul_Hossler View Post
I hadn't thought about a 'severity score' based on the error number (1000-1999 = mild, 2000-2999 = medium, 3000-3999 = sever) but that's not a bad idea
Heh, not what i had in mind. I wouldn't combine two distinct pieces of information, if it can be avoided. Severity may be contextual. A corrupt workbook might be fatal for some apps, but ok to ignore and skip for other apps. I would have done:

Enum CustomErr
          UserCancel = vbObjectError
          UserPause
          ProtectedWorkbook
          CorruptWorkbook
          ShellError
End Enum


Enum ErrorSeverity
          Mild
          Medium
          Severe
End Enum

And then put Severity in Err.Description. Or maybe it could be And'ed or Or'd with error-number, and together put into Err.Number?