WD2000: Converted WordBasic On Error Statements May Fail (202019)
The information in this article applies to:
This article was previously published under Q202019 SYMPTOMS
When you run a Microsoft Visual Basic for Applications procedure or macro
that was converted from a WordBasic procedure or macro that contained error
trapping, the error trap is ignored, although it worked as expected when run
in WordBasic.
CAUSEMicrosoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
By design, the On Error statement in Visual Basic for Applications works differently from the way it does in WordBasic. In Visual Basic for Applications, On Error is not cleared when an error occurs.
In WordBasic, the On Error statement is cleared, the error trap is
reset, and your code continues to run.
Therefore, the following sample converted WordBasic code fails when an
error occurs the second time.
Sub Main()
' Clear error trap. Set error trap.
On Error GoTo -1: On Error GoTo ErrorTrap
' Loop 10 times.
For i = 1 To 10
' Artificially raise an error.
Err.Raise 5
ErrorTrap:
' Decision tree based on error returned.
If Err.Number = 0 Then
' If no error occurred, do this...
count_ = count_ + 1
Else
' Else, if error occurred, do this...
Err.Number = 0
End If
Next
End Sub
WORKAROUND
To work around this issue, make the On Error statement the first statement
inside the loop.
Sub Main()
' Loop 10 times.
For i = 1 To 10
' Clear error trap. Set error trap.
On Error GoTo -1: On Error GoTo ErrorTrap
' Artificially raise an error.
Err.Raise 5
ErrorTrap:
' Decision tree based on error returned.
If Err.Number = 0 Then
' If no error occurred, do this...
count_ = count_ + 1
Else
' Else if error occurred, do this...
Err.Number = 0
End If
Next
End Sub
In this example, the Err.Raise statement artificially raises an error for
demonstration purposes. When the error occurs and the next iteration of the
loop occurs, the On Error GoTo -1 statement clears the error trap and the
On Error GoTo ErrorTrap statement resets the error trap. The loop
continues to process without interruption until it completes the designated
number of iterations (10).
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. REFERENCESFor more information about on error statement, in the Visual Basic Editor, click Microsoft Visual Basic Help on the Help menu, type on error in the Office Assistant or the Answer Wizard, and then click Search to view the topic.
For more information about getting help with Visual Basic for Applications,
please see the following article in the Microsoft Knowledge Base:
226118 OFF2000: Programming Resources for Visual Basic for Applications
Modification Type: | Major | Last Reviewed: | 6/17/2005 |
---|
Keywords: | kbbug kbmacroexample kbnofix kbProgramming KB202019 |
---|
|