The VB.NET group is a forum where peers share technical expertise, solve problems, and discuss issues related to the Visual Basic .NET programming environment, including coding issues, fundamentals, and technologies.

I think you have to use the Win32 API and end the process.
I know we had a process recently from VB.NET that fired up Word to generate a document.
Word would not close down either.
I had to go to the server periodically and kill all the Word instances ( it would spin up a new one for each document ).

Almost forgot... If you try the Win32 terminate process call, be aware, the user may have other Excel instances open, you might ( probably ) end up killing theirs and leaving yours open. There wasn't a way thru the COM stuff to determine that instance of the apps process id.

I know this is C# the idea here is to give you the objects you need to deal with. You have to pound on COM objects to get them cleaned up. Note too many of these things will throw errors if the object being killed is already gone so test before firing.

Thank you all for your help. The simple "Application.Quit" worked functionally. However, I see that getting everything cleaned up via Garbage Cleaning is a more complicated than I had imagined.

I plan to try some combination of your suggestions regarding getting all residual leftovers out of memory. As suggested, I'll check with the "Task Manager" to see if anything is still "running" after I get out of my VB.NET application that opens Excel.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.