Microsoft KB Archive/164556

= WD97: Two Similar Macro Errors Occur for Same Line of Macro Code =

Article ID: 164556

Article Last Modified on 7/16/2007

-

APPLIES TO


 * Microsoft Word 97 Standard Edition

-



This article was previously published under Q164556





SYMPTOMS
When you run a macro that contains code using the WordBasic Object in Visual Basic for Applications, you may receive two similar errors. One error is a Visual Basic for Applications error, and the other error is a WordBasic error.



CAUSE
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals 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 needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

The duplicate or similar errors are the result of using the WordBasic Object to call WordBasic commands within a Visual Basic for Applications environment. In certain situations, if an error occurs, you will receive a Visual Basic for Applications error and a WordBasic error.

Furthermore, if the error number returned is greater than 1000, the WordBasic error cannot be trapped.

The following converted WordBasic macro example, when run in Visual Basic for Applications, will create duplicate errors if the file name you are attempting to open does not exist. The On Error statement will trap the Visual Basic for Applications error but it cannot trap the resulting WordBasic error. If you comment the On Error command line, two errors will occur when you attempt to open the non-existent file: "Microsoft Word error 1078" and "Microsoft Visual Basic run time error 1078." Sub MAIN Dim MissingFile$ On Error Resume Next MissingFile$ = "Macintosh HD:NoFile" WordBasic.FileOpen Name:=Chr(34) + MissingFile$ + Chr(34) End Sub

