How do I use MrDebug's Error system?
 We recommended the following changes to your error system.
──────────────────────────────────────────────────────────────────────────────

 Included with MrDebug is an example error system, _MrDErSy.PRG that includes
 some of the changes that you should make to your system's to enable them to
 work effectively with MrDebug.

 Many of you have written your own error systems that have their own special
 qualities. The following section will guide you through the changes needed
 to take full advantage of MrDebug.

 There are a few problems with CA-Clipper's GT system handling of unexpected
 screen modes for which CA-Clipper was not designed to handle. An example of
 this is when you are running MrDebug in a text mode of 132 columns by 60
 rows and your application screen is set to 80 columns by 25 rows.

 The problem lies somewhere within either __gtPreExt or __gtPostExt.
 Basically, it causes the application screen to become garbled.

 To work around this problem:

    Replace all occurrences of 'STDOUT()' with '?'

    If you have any lines within either your error system or the standard
    error system that do something similar to the following

         #command ? <list,...>   =>  ?? Chr(13) + Chr(10) ; ?? <list>
         #command ?? <list,...>  =>  OutErr(<list>)

    then comment them out.

 NOTE: If you have to use STDOUT with MrDebug, then it is possible. You must
       run your application in full screen mode with screen swapping turned
       on and Force Application into 80x25 turned off.

 To enable MrDebug to capture an error object from your application and
 display it in an error window, where you may browse and edit the object, add
 the following line to your error system:

                MrdSaveErr(oError)

 This will allow MrDebug to save any error, if it occurs, and display it in
 an Error Window. You may then select this window, if not already selected,
 and press ◄──┛ to display further details of the error object.