- An untreated error in a program will cause execution to stop and an error message is displayed to the user, who can choose to continue (ignore the error - which could have unexpected results) or end the program.
- Use ON ERROR when your program performs operations that are likely to generate errors, like file access operations.
- ON ERROR statements can be in the main module code or in SUB or FUNCTION procedures.
- ON ERROR statements take precedence in the order they are encountered. It will also handle any subroutine errors.
- ON ERROR GOTO 0 can be used to disable custom ON ERROR trapping and give default error messages.
- A subsequent ON ERROR statement will override the previous one.
- GOTO is required in the statement. Cannot use GOSUB.
- Comment out ON ERROR to find specific error locations. QB64 can return the file line position with _ERRORLINE
- Note: QB64 does not support the PDS (QuickBASIC 7) ON ERROR RESUME NEXT statement.
Using an error handler that ignores any error.
ON ERROR GOTO Errhandler
' Main module program error simulation code
ERROR 7 ' simulate an Out of Memory Error
PRINT "Error handled...ending program"
SYSTEM ' end of program code
Errhandler: 'error handler sub program line label
PRINT "Error"; ERR; "on program file line"; _ERRORLINE
BEEP ' warning beep
RESUME NEXT ' moves program to code following the error.
Error 7 on program file line 3
Error handled...ending program
Explanation: The ON ERROR statement is normally placed at the beginning of the main module code. Errhandle is the line label sub referred to in the statement. The handler prints the error code and attempts to use the next line of code using RESUME NEXT which is only used in error handling procedures. _ERRORLINE returns the program file’s actual text line count found in the IDE.
Using an error handler in a SUB procedure.
PRINT "got error!"
ON ERROR GOTO hand
ON ERROR GOTO 0