It doesn't specify line 0 as the start of the error-handling code, even if the procedure contains a line numbered 0. On Error GoTo 0 disables error handling in the current procedure.
#Excel vba on error goto errorhandler code
You can be sure which object placed the error code in Err.Number, as well as which object originally generated the error (the object specified in Err.Source). Checking Err after each interaction with an object removes ambiguity about which object was accessed by the code.
Note The On Error Resume Next construct may be preferable to On Error GoTo when handling errors generated during access to other objects. An On Error Resume Next statement becomes inactive when another procedure is called, so you should execute an On Error Resume Next statement in each called routine if you want inline error handling within that routine. You can place the error-handling routine where the error would occur, rather than transferring control to another location within the procedure. This statement allows execution to continue despite a run-time error. On Error Resume Next causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. The error message associated with Err.Number is contained in Err.Description. The property values in the Err object reflect only the most recent error. The error-handling routine should test or save relevant property values in the Err object before any other error can occur or before a procedure that might cause an error is called.
It is a section of code marked by a line label or line number.Įrror-handling routines rely on the value in the Number property of the Err object to determine the cause of the error. Note An error-handling routine is not a Sub procedure or Function procedure. Once an error is handled by an error handler in any procedure, execution resumes in the current procedure at the point designated by the Resume statement. Each time the error handler passes control back to a calling procedure, that procedure becomes the current procedure. If no inactive, enabled error handler is found, the error is fatal at the point at which it actually occurred. If the calling procedure's error handler is also active, control passes back through previous calling procedures until an enabled, but inactive, error handler is found. If the calling procedure has an enabled error handler, it is activated to handle the error. Control returns to the calling procedure. If an error occurs while an error handler is active (between the occurrence of the error and a Resume, Exit Sub, Exit Function, or Exit Property statement), the current procedure's error handler can't handle the error. If you don't use an On Error statement, any run-time error that occurs is fatal that is, an error message is displayed and execution stops.Īn "enabled" error handler is one that is turned on by an On Error statement an "active" error handler is an enabled handler that is in the process of handling an error. This extract from help seems to cover it (at least to me) On Error Goto 0 - Disables any enabled error handler in the current procedure.
0 kommentar(er)
