Important Notice

The pages on this site contain documentation for very old MS-DOS software, purely for historical purposes. If you're looking for up-to-date documentation, particularly for programming, you should not rely on the information found here, as it will be woefully out of date.

  ◄Summary►  ◄Details►  ◄Example►                ◄Contents►  ◄Index►  ◄Back►
──────────────────────────────────────────────────────────────────────────────
 RESUME [{line | NEXT}]
 
 Usage Notes
   ■ The location where execution resumes is based on the location of the
     error handler in which the error is trapped, not on the location where
     the error occurred.
 
   ■ If Visual Basic has to search for the error handler, and the error
     handler that contains the RESUME statement is in a procedure or module
     other than the one in which the error occurred, then the last statement
     executed in that procedure or module is the last call out of that
     procedure or module.
 
   ■ As a rule, avoid using a line argument with a RESUME statement in a
     module-level error handler, unless you expect errors to occur only at
     the module level.
 
   ■ A RESUME statement that is not in an error-handling routine produces the
     error message, "RESUME without error."
 
   ■ When an error-handling routine is active, if the end of the program
     text is encountered before executing a RESUME statement, Visual Basic
     generates the error message, "No RESUME." This is also true if an END,
     END SUB, END FUNCTION, or END DEF statement (for a local error handler)
     is executed before a RESUME statement.
 
   ■ When you are compiling from the BC command line, programs that contain
     error-handling routines must be compiled with either the /E (ON ERROR)
     or /X (RESUME NEXT) option. See: ◄BC command-line options►