OK, now I am confused. All along I thought that .Net CreateObject was
not instantiating a new copy of XL. But, in your latest post you
indicate that you are. So, what problem are you are trying to resolve?

--
Regards,

Tushar Mehta
www.tushar-mehta.com
Excel, PowerPoint, and VBA add-ins, tutorials
Custom MS Office productivity solutions

In article ,
am says...
It has something to do with how the XP launches a file associated with an
exe. If I click on or choose, open form the context menu in the file
explorer the workbook is loaded into the most recently launched instance of
Excel or if I launch the file alone form the command line it is put into the
most recently launched instance of Excel. If I launch Excel and then load
the file I get a separate instance of Excel or if I launce excel from the
command line with the file as a command line argument I get a second instance
of excel.
I know .NET launches a new instance of Excel because I can wind up with
several running. I can verify this by the tasks manager. I will have
several Excels running that I need to explicitly end them.
A quick check of Word and Visio; Visio is similar Excel and Word is
different. Word under the Windows menu you can see all the running documents
but closing there window only closes the one document.