ErrorHandle - Error handle
Inherits: 
RessourceLock
The default error handle provides basic functions for writing error messages or information to a log and a protocol file ( error.lst and protocol.lst ). The location for those files is retrieved from the TRACE option variable. In windows applications messages can be displayed also in a message box by activating GUI-messages.
The error handle can be overloaded in applications or subsystems by more specific error handles. Thus, e.g. database applications usually use the DBErrorHandle, which allows accessing multilingual error definitions in a resource database.
Attributes
Functions
- ActivateGUIMessages - Activate GUI messages
- AddError - Register error object
- DeactivateGUIMessages - - internal feature (not documented)
- DisplayMessage - Display message
- ErrorHandle - Constructor
- GUIMessagesActivated - Are GUI messages activated?
- GetDecision - Get decision
- GetError - - Title unknown
- GetErrorDescription - Get help context id
- GetProtocolPath - - internal feature (not documented)
- GetTracePath - Get location for protocol file and error log
- InsertStatField - Insert status line field
- IsValid - - internal feature (not documented)
- OutputMessage - Write message to system output
- RemoveError - Unregister error object from handle
- RemoveStatField - Remove user field from the status line
- ResetAllErrors - Reset all errors
- SetBusy - - Title unknown
- SetLanguage - Select language for error messages
- SetStatField - Set value in status line
- SetStatText - Set status line text
- SetTracePath - Set path for error-log file
- ShowMessage - Show message
- Terminate - Terminate application
- WriteError - Write error to the log-file
- WriteProtocol - - Title unknown
- WriteProtocolText - - internal feature (not documented)
- WriteTrace - Write trace message
- ~ErrorHandle - Destructor

