B
Bob
I am running Windows XP Pro with SP1 and Office XP.
When I start OUTLOOK, there is also a copy of WINWORD that gets started.
When I close OUTLOOK, the WINWORD continues to exist.
This becomes a problem when I run the VB program I have written which
generates WORD documents. If there is an existing copy of WinWord running,
then I ge all sorts of strange errors including putting text into a
previously open document. I have to ensure that there is no other copy of
WINWORD running before executing my program.
Has anyone else noticed this phantom execution of WINWORD on their systems?
How I can determine at runtime that there is no copy of WINWORD already
running?
Thanks for any insights
Bob
When I start OUTLOOK, there is also a copy of WINWORD that gets started.
When I close OUTLOOK, the WINWORD continues to exist.
This becomes a problem when I run the VB program I have written which
generates WORD documents. If there is an existing copy of WinWord running,
then I ge all sorts of strange errors including putting text into a
previously open document. I have to ensure that there is no other copy of
WINWORD running before executing my program.
Has anyone else noticed this phantom execution of WINWORD on their systems?
How I can determine at runtime that there is no copy of WINWORD already
running?
Thanks for any insights
Bob