WORKAROUND
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.
To demonstrate the problem, the following Visual Basic macro creates a new invisible document:
Sub Test()
Application.Documents.Add
ActiveDocument.ActiveWindow.Visible = False
End Sub
When you view the Windows List on the
Window menu, the new invisible document appears as a selectable item with the symptoms listed at the beginning of this article.
To avoid this situation, Visual Basic for Applications developers should use the
Visible property with due precautions and never leave an invisible document around after a code block is done processing with it. The invisible document created in the code block above can be closed without any prompt to save changes with the additional line of code in the example below:
Sub Test()
Application.Documents.Add
ActiveDocument.ActiveWindow.Visible = False
.
.
.
' Close the hidden document without save changes.
ActiveDocument.ActiveWindow.Close SaveChanges:=wdDoNotSaveChange
End Sub