W
William Wong
Dear all,
My office computers were recently upgraded to Vista and Office 2007 and I
notice a very strange problem: WinWord (and others) would not quit itself
completely when user press the "X" button after it opened any file on
network shares. Although there is no winword found on the desktop, I can see
a list of multiple instances of winword.exe in task manager consuming memory
just by hanging there. Manually disabling all COM AddIn or running winword
as "winword /a" has no problem in quitting itself but neither of them is an
acceptable solution. BTW, winword has no problem in closing itself
completely when there are only files resized on local hard disk being
opened. Any clue?
William
My office computers were recently upgraded to Vista and Office 2007 and I
notice a very strange problem: WinWord (and others) would not quit itself
completely when user press the "X" button after it opened any file on
network shares. Although there is no winword found on the desktop, I can see
a list of multiple instances of winword.exe in task manager consuming memory
just by hanging there. Manually disabling all COM AddIn or running winword
as "winword /a" has no problem in quitting itself but neither of them is an
acceptable solution. BTW, winword has no problem in closing itself
completely when there are only files resized on local hard disk being
opened. Any clue?
William