You best bet is to fix the dodgy code, but as Jake pointed, excel is not
supposed to be run like this.
Probably due to the use of unqualified object that are not released, so
error state not properly handled.

Process Explorer from SysInternals will tell you which files are being used
by each Excel instance. may help track down the culprit.

If you feel you want to automate it, rather than actually fix the cause:
http://www.thescarms.com/vbasic/StopProcess.asp

NickHK

"JB2005" wrote in message
...
Situation: Inactive or incorrectly terminated Excel process images
accumulate
on server

Anyone out there with knowledge/advice on how to access a hung(?) instance
of Excel and pull information about the calling event or anything else
that
may help identify the root cause?

Any auditing techniques out there that can record such events?

Your help much appreciated.