> Dear All,
>
[quoted text clipped - 13 lines]
> Regards,
> Jim
If it shows in the "Applications" tab in TaskManager, you may be able to
find the window and shut it down externally. Basically, yank its plug (kill
the process), it's a bit tougher if it only shows in the "Processes" tab but
still possible.
There's several "Process Related" samples here that may help...
http://www.thescarms.com/vbasic/VBProcessRelated.asp
If that AxEXE's linked to multiple exe's, it can get tricky. If it's just
for 1 exe, a decent way to let it kill itself is to raise an event every
second or so that passes a ByRef argument. The client app can change the
contents of that and return. If it comes back without any change, you know
there's no client listening. At that time, you can release all objects,
close forms, stop timers, whatever and the AxEXE should die on its own.

Signature
Ken Halter - MS-MVP-VB - http://www.vbsight.com
DLL Hell problems? Try ComGuard - http://www.vbsight.com/ComGuard.htm
Please keep all discussions in the groups..
Jim Chen - 24 Jun 2005 09:11 GMT
Thank you very much Ken. It helps a lot.
Jim
>> Dear All,
>>
[quoted text clipped - 28 lines]
> there's no client listening. At that time, you can release all objects,
> close forms, stop timers, whatever and the AxEXE should die on its own.