Class: ErrorSystem

This allows us to skip find errors (GT & LT) and to only ring a bell when these occur.

Flag which is sent when error is being processed. This stops error recursion.

shows error numbers with user errors. Only set this true if your application has meaningful numbers that helps the end user. Note that unhandled errors always show numbers. this is ignored if pbUnhandledErrorSupport is false

If set false, this makes the error handler work the old way which does not use the new unhandled dialog. Only exists for compatibility reasons

This is the caption that appears for unhandled errors dialog box

This is the caption that appears for standard user errors

array of errors that we consider User Errors

adds a user error to the array

*** Build complete error description from Flexerrs and user error message.

*** Handle error event, displaying error info to user.

JJT- Note if you are using the WINDAF windows help system the following functions are not used. The functions below are used to construct a general help name for errors that are generated by the system. If processing comes here, then there was no module specific help found. These functions will provide a more general help name that appears in the form of SYSTEM..ERROR:#. All global errors should be places in the help file under this application and module name. *** Returns "ERROR:errornum" to supply error help.

*** Forward all error to regular DataFlex error handler.

*** Pass error Error# on to the regular DataFlex error handler.

** return true if an error number is critical

returns true if this is an unhandled error (i.e., not a user error

removes all user errors

removes an error from the user array

*** Catch and display all errors.

*** Catch and display error Error#.