Run-time errors can occur when compiled application code is run. The two types of run-time errors are: Recoverable and None- Recoverable errors
Non-recoverable run-time errors
Recoverable run-time errors
If the application contains a run-time error that is not handled by ATEasy's default error handler code, a default error handler dialog box shows the error number, a short description, the line number where the error occurred, and the options you can take. At the same time, a code view window displays on top showing the statement causing the error, marked with an arrow.
The run-time error may be a non-recoverable error or a recoverable error.
A non-recoverable error displays a default error handler dialog box that allows you the option to either Abort or Pause the application.
Abort terminates the application (which is different from the Abort for a recoverable run-time error).
Pause stops the application and ATEasy shows you where the fatal error occurred. During this special pause state, you can examine the application, variables, and any causes for why the error occurred. If you press Continue while in this paused state, the application will terminate.
Recoverable run-time errors mainly occur within I/O Tables on the failure of a Send or Receive operation.
A recoverable error displays a default error handler dialog box that allows you the option to Ignore, Retry, Abort, or Pause the application.
Ignore continues with the execution to the next statement and bypasses the error.
Retry repeats the statement that caused the error.
Abort stops the application with the Abort statement, calling the application's OnAbort events.
Pause stops the application and ATEasy shows you where the fatal error occurred. During this special pause state, you can examine the application, variables, and any causes for why the error occurred. If you press Continue while in this paused state, the application will abort.
You can handle the error with the Try and Catch block and OnError() event. Using the Try and Catch block, you can apply a precise fix to find the statement where the error occurred. If there is no Try... Catch block surrounding the code, ATEasy will try to call the OnError() event in the module that caused the error.
For more information on handling errors, see Error and Exception Handling.