WINWORD.EXE still active in Task Manager

  • Thread starter Thread starter Glenn De Tollenaere
  • Start date Start date
G

Glenn De Tollenaere

Hi all,

I have a major problem. In my application I start Word, by
means of OLE. By starting it up, a macro is run (the macro
resides in a .dot file that is stored in the startup
folder of Word, eg \Program Files\Microsoft
office\office\startup) that builds a custom commandbar
with some buttons on it. If I close my application, Word
is being stopped too. It seams however that WINWORD.EXE
stays in the tasklist !!!

If I do not use the .dot file in the startupfolder,
everything works fine (so WINWORD.EXE dissapears out of
the tasklist, which is correct).

I suspect this has something to do with the fact Word
thinks the normal.dot file is being changed (if I close my
application, Word is being closed and you can see for a
second that Word is saving normal.dot).

Any suggestions are welcome, because once Word has been
opened, it seems to hold a lock on this normal.dot-file so
the second time Word is started from within my application
I get several problems closing Word.

Regards
Glenn
 
Hi Glenn,

Hard to say, without seeing the code that instantiates Word
and any object in Word, and the corresponding code that
releases all these objects and quits Word. You do explicitly
release the object pointers and Quit the Word application?
I have a major problem. In my application I start Word, by
means of OLE. By starting it up, a macro is run (the macro
resides in a .dot file that is stored in the startup
folder of Word, eg \Program Files\Microsoft
office\office\startup) that builds a custom commandbar
with some buttons on it. If I close my application, Word
is being stopped too. It seams however that WINWORD.EXE
stays in the tasklist !!!
Click to expand...

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jan
24 2003)
http://www.mvps.org/word

This reply is posted in the Newsgroup; please post any follow
question or reply in the newsgroup and not by e-mail :-)
 
Hi Cindy,

yes indeed. The problem only occurs if I use the specific
template (.dot in the startup folder). If I rename this
one to .do for instance (so Word won't load it), and
perform the same actions, quit Word in my application all
works fine !

Of course the normal.dot isn't being modified at that
time, so maybe that is the problem ?

This is a very annoying thing, because once Word has been
activated the user gets errors (saying normal.dot is being
modified by someone else and so on).

Any of your suggestions to solve it are welcome.

Regards
Glenn
http://www.advosoft.be
 
Back
Top