U
Urs Eichmann
Hi there
Scenario: I have a VB.NET appliaction which uses DSOFramer to embed Word
into a Windows Forms application. The embedded word instance only lives
while the application shows a Word document and is disposed after
closing the form.
This principally works fine. BUT - if the user happens to start a
stand-alone instance of Word by using the Start Menu while my
application still shows the embedded Word instance, nothing happens. If
the user repeats the start-up process, then a stand-alone instance
shows, but somehow crippled, i.e. it seems somehow mixed-up with my own
embedded instance. Also, if I close my VB.NET application after the user
started a stand-alone instance, the WINWORD.EXE process keeps running,
as can be seen in the Task Manager.
I discovered that, if the user starts the stand-alone instance with the
/W flag, it works fine. The embedded instance and the stand-alone
instance then behave separately. My question is, is there ANOTHER way of
separating user and automation instances? Since this is going to be a
wide-spread application, it is VERY error-prone, and will be a nightmare
to support, if we have to tell all the users to change their start menu
links. And then there is also the problem when a user double-clicks on a
..DOC file....
Any help or insight would be greatly appreciated.
Urs
Scenario: I have a VB.NET appliaction which uses DSOFramer to embed Word
into a Windows Forms application. The embedded word instance only lives
while the application shows a Word document and is disposed after
closing the form.
This principally works fine. BUT - if the user happens to start a
stand-alone instance of Word by using the Start Menu while my
application still shows the embedded Word instance, nothing happens. If
the user repeats the start-up process, then a stand-alone instance
shows, but somehow crippled, i.e. it seems somehow mixed-up with my own
embedded instance. Also, if I close my VB.NET application after the user
started a stand-alone instance, the WINWORD.EXE process keeps running,
as can be seen in the Task Manager.
I discovered that, if the user starts the stand-alone instance with the
/W flag, it works fine. The embedded instance and the stand-alone
instance then behave separately. My question is, is there ANOTHER way of
separating user and automation instances? Since this is going to be a
wide-spread application, it is VERY error-prone, and will be a nightmare
to support, if we have to tell all the users to change their start menu
links. And then there is also the problem when a user double-clicks on a
..DOC file....
Any help or insight would be greatly appreciated.
Urs