If I start an instance of a word application via COM Interop, an instance of Winword.exe is started in the background. If I then subsequently load a Word document from Windows Explorer, it is loaded into the running Winword.exe process that was created via the COM Interop calls.
When my application then closes the COM Interop Application object (because it's done with it), all documents that were loaded into it from Windows Explorer are also shut.
Is there any way to prevent "Native" Microsoft Word from re-using a Winword.exe process that was generated via COM Interop?
Update: Corporate environment so running under another user account isn't feasible.
Update: Word versions range from 2003 on most users machines to 2010 on others.
Update: The workaround described On this KB is only partially adequate as it doesn't work with opening of documents from windows explorer.