WD2000: Word Disappears from Screen but Remains in Memory When You Use LookIn Property (244354)

The information in this article applies to:

Microsoft Word 2000

This article was previously published under Q244354

SYMPTOMS

When you use the LookIn property in your code in the Microsoft Visual Basic Editor to perform a file search, and you then run this code while Microsoft Word is open, Word disappears from your screen but remains in memory.

For example, if you type the following code in a module in the Visual Basic Editor, and you then run the code, Word disappears from your screen but remains in memory:

Sub test()
With Application.FileSearch
    .FileName = "*.*"
    .LookIn = " "
    .Execute
    For I = 1 To .FoundFiles.Count
        MsgBox .FoundFiles(I)
    Next I
End With
End Sub

CAUSE

This behavior occurs when a space is assigned to the LookIn property.

WORKAROUND

To work around this behavior, ensure that your code does not accept spaces as user inputs for the LookIn property when performing file searches.

STATUS

Microsoft has confirmed that this is a problem in Microsoft Word 2000.

MORE INFORMATION

To determine whether Word is in memory, follow these steps:

Right-click the taskbar on your Windows desktop, and then click Task Manager.
In the Windows Task Manager dialog box, click the Processes tab.
If Word is in memory, Winword.exe is in the list of processes.

REFERENCES

For more information about the Microsoft Visual Basic Editor, click Microsoft Word Help on the Help menu, type get help for visual basic for applications in word in the Office Assistant or the Answer Wizard, and then click Search to view the topics returned.

For more information about the LookIn property, click Microsoft Visual Basic Help on the Help menu, type lookin property in the Office Assistant or the Answer Wizard, and then click Search to view the topic.

Modification Type:	Major	Last Reviewed:	12/6/2000
Keywords:	kbbug KB244354