The information on this page applies to: | |
---|---|
MathType for Windows | Microsoft Word for Windows |
C:Program Files (x86)MathTypeMathPage32
C:Program Files (x86)MathTypeMathPage64
C:Users[user name]AppDataRoamingMicrosoftWordSTARTUP
C:Program Files or Program Files(x86)Microsoft OfficerootOffice16STARTUP
C:Users[user name]AppDataLocalPackages
Microsoft.Office.Desktop_8wekyb3d8bbweLocalCacheRoamingMicrosoftWordSTARTUP
On Error
statement is used in unstructured error handling and can be used instead of structured exception handling. Structured exception handling is built into .NET, is generally more efficient, and so is recommended when handling runtime errors in your application.Error
keyword is also used in the Error Statement, which is supported for backward compatibility.Term | Definition |
---|---|
GoTo line | Enables the error-handling routine that starts at the line specified in the required line argument. The line argument is any line label or line number. If a run-time error occurs, control branches to the specified line, making the error handler active. The specified line must be in the same procedure as the On Error statement or a compile-time error will occur. |
GoTo 0 | Disables enabled error handler in the current procedure and resets it to Nothing . |
GoTo -1 | Disables enabled exception in the current procedure and resets it to Nothing . |
Resume Next | Specifies that when a run-time error occurs, control goes to the statement immediately following the statement where the error occurred, and execution continues from that point. Use this form rather than On Error GoTo when accessing objects. |
On Error
statement. For more information, see Try...Catch...Finally Statement.On Error
statement. An 'active' error handler is an enabled handler that is in the process of handling an error.Resume
, Exit Sub
, Exit Function
, or Exit Property
statement), the current procedure's error handler cannot handle the error. Control returns to the calling procedure.Resume
statement.Sub
procedure or a Function
procedure. It is a section of code marked by a line label or a line number.Number
property of the Err
object to determine the cause of the error. The 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. The property values in the Err
object reflect only the most recent error. The error message associated with Err.Number
is contained in Err.Description
.Err.Raise
method sets the Exception
property to a newly created instance of the Exception class. In order to support the raising of exceptions of derived exception types, a Throw
statement is supported in the language. This takes a single parameter that is the exception instance to be thrown. The following example shows how these features can be used with the existing exception handling support:On Error GoTo
statement traps all errors, regardless of the exception class.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. This statement allows execution to continue despite a run-time error. You can place the error-handling routine where the error would occur rather than transferring control to another location within the procedure. 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.On Error Resume Next
construct may be preferable to On Error GoTo
when handling errors generated during access to other objects. Checking Err
after each interaction with an object removes ambiguity about which object was accessed by the 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
).On Error GoTo 0
disables error handling in the current procedure. It doesn't specify line 0 as the start of the error-handling code, even if the procedure contains a line numbered 0. Without an On Error GoTo 0
statement, an error handler is automatically disabled when a procedure is exited.On Error GoTo -1
disables the exception in the current procedure. It does not specify line -1 as the start of the error-handling code, even if the procedure contains a line numbered -1. Without an On Error GoTo -1
statement, an exception is automatically disabled when a procedure is exited.Exit Sub
, Exit Function
, or Exit Property
statement immediately before the error-handling routine, as in the following fragment:Exit Sub
statement and precedes the End Sub
statement to separate it from the procedure flow. You can place error-handling code anywhere in a procedure.Err.Number
to one of your own errors and then pass them back to the caller of your object. You should specify your error by adding your error code to the VbObjectError
constant. For example, if your error code is 1052, assign it as follows:Err
object's LastDLLError
property.On Error GoTo
statement to specify the location of an error-handling routine within a procedure. In the example, an attempt to divide by zero generates error number 6. The error is handled in the error-handling routine, and control is then returned to the statement that caused the error. The On Error GoTo 0
statement turns off error trapping. Then the On Error Resume Next
statement is used to defer error trapping so that the context for the error generated by the next statement can be known for certain. Note that Err.Clear
is used to clear the Err
object's properties after the error is handled.