Occurs when a serious execution time error occurs (such as trying to open a nonexistent window) if the error is not handled in a try-catch block.
Event ID |
Objects |
|---|---|
None |
Application |
None
None. (Do not use a RETURN statement.)
If there is no script for the SystemError event, PocketBuilder displays a message box with the PocketBuilder error number and error message text.
For errors involving external objects and DataWindows, you can handle the error in the ExternalException or Error events and prevent the SystemError event from occurring. The ExternalException and Error events are maintained for backward compatibility.
You can prevent the SystemError event from occurring by handling errors in try-catch blocks. Well-designed exception-handling code gives application users a better chance to recover from error conditions and run the application without interruption. For information about exception handling, see the Resource Guide.
When a SystemError event occurs, your current script terminates and your system might become unstable. It is generally not a good idea to continue running the application, but you can use the SystemError event script to clean up and disconnect from the DBMS before closing the application.
This statement in the SystemError event halts the application immediately:
HALT CLOSE
