Article ID: 181538
Article Last Modified on 6/17/2005
APPLIES TO
- Microsoft Word 98 for Macintosh
This article was previously published under Q181538
SYMPTOMS
When you run a recorded macro that performs the following actions:
- Changes to Outline View -and-
- Saves the file -and-
- Closes the document -and-
- Opens the document
you receive the following error message:
CAUSE
The "ActiveWindow.ActivePane.View.Type=wdOutlineView" statement is recorded a second time in the macro when the document is closed.
WORKAROUND
Comment or delete the second occurrence of the following statement in the recorded macro:
ActiveWindow.ActivePane.View.Type = wdOutlineView
NOTE: The second occurrence of this statement in the sample macro in the "More Information" section of this article immediately follows the "ActiveDocument.Close" statement.
To Comment the Problematic Line of Code
Visual Basic ignores comments when it runs your procedures. Comment lines begin with an apostrophe (') or with Rem followed by a space, and can be added anywhere in a procedure. Follow these steps to convert the problematic line of code to a comment:
- In the open document, point to Macro on the Tools menu, and then click Macros.
- Select the recorded macro, and then click Edit.
- In the Visual Basic Editor, select the line of macro code that you want to convert to a comment.
- On the View menu, point to Toolbars, and then click Edit.
On the Edit toolbar, click the Comment Block button. The line of macro code should now look similar to the following:
' ActiveWindow.ActivePane.View.Type = wdOutlineView
Note the apostrophe at the beginning of the line.
- On the File menu, click "Close and Return to Microsoft Word."
To Delete the Problematic Line of Code
- In the open document, point to Macro on the Tools menu, and then click Macros.
- Select the recorded macro, and then click Edit.
- In the Visual Basic Editor, select the line of macro code you want to delete.
- On the Edit menu, click Cut.
- On the File menu, click "Close and Return to Microsoft Word."
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.
MORE INFORMATION
Microsoft 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. When you record the macro as described in the "Symptoms" section of this article, the recorded macro may look similar to the following:
Sub Test() ActiveDocument.SaveAs FileName:="test.doc",FileFormat:= _ wdFormatDocument, LockComments:=False, Password:="", _ AddToRecentFiles:=True, WritePassword:="", _ ReadOnlyRecommended:=False, EmbedTrueTypeFonts:=False, _ SaveNativePictureFormat:=False, SaveFormsData:=False, _ SaveAsAOCELetter:=False ActiveWindow.ActivePane.View.Type = wdOutlineView ActiveDocument.Save ActiveDocument.Close ActiveWindow.ActivePane.View.Type = wdOutlineView Documents.Open FileName:="test.doc", ConfirmConversions:=False, _ ReadOnly:= False, AddToRecentFiles:=False, PasswordDocument:="", _ PasswordTemplate:= "", Revert:=False, WritePasswordDocument:="", _ WritePasswordTemplate:="", Format:=wdOpenFormatAuto End Sub
REFERENCES
For more information about getting help with Visual Basic for Applications, please see the following article in the Microsoft Knowledge Base:
163435 VBA: Programming Resources for Visual Basic for Applications
Additional query words: wordcon
Keywords: kbbug kbnofix kbmacro kbdtacode KB181538