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
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