So this took me longer to spot than I'd like to admit...
When Vba goes bad and a hidden excel application object is orphaned, the instance is still running.
I am used to ending the process (not application) Excel.exe in Windows 7 via task manager. Now I have Windows 10 and it says "Microsoft Excel..." which is only part of the name and all I am going to bother to remember as that is enough to find it.
Technically this is not a vba question but what is it different? Or how would I find out what an orphaned application would be in task manager when automating?
When Vba goes bad and a hidden excel application object is orphaned, the instance is still running.
I am used to ending the process (not application) Excel.exe in Windows 7 via task manager. Now I have Windows 10 and it says "Microsoft Excel..." which is only part of the name and all I am going to bother to remember as that is enough to find it.
Technically this is not a vba question but what is it different? Or how would I find out what an orphaned application would be in task manager when automating?