Observing logic errors

When a Superbase program has a logic error, it will either done one of 4 things, depending on the author of the program:

Stop and put up and error dialog (called a Requestor in Superbase terminology) and wait for someone to acknowledge it.

Display an error on the status bar

Show nothing

Crash or cause a General Protection Fault (GPF or UAE)

When you observe a logic error, your best course of action is to figure out where the program is executing and once you have nailed this down, use the DEBUG and output facilities to track down the logic in the program until you can locate the problem and eliminate it.

Some Superbase developers write a "generic" error handling routine to catch all errors and either take some action, which may even include writing into a textual log file or a database of errors.

The Superbase Help File contains a list of all error messages, sorted in alphabetical order, and also sorted in numerical order (since every error has an error number associated with it)

See the section on using the debugger and troubleshooting for more information.