> I have an app that if killed by terminating the process, does not seem to
be
> notified in a way that I can detect to clean up (ie. no onclose,
formdestroy
> etc), in essence no message seems to be sent to pick up.

> Any ideas on how to trap this case of program closure ?

> Regards

> nick

> I have an app that if killed by terminating the process, does not seem to be
> notified in a way that I can detect to clean up (ie. no onclose, formdestroy
> etc), in essence no message seems to be sent to pick up.

> > I have an app that if killed by terminating the process, does not seem
to be
> > notified in a way that I can detect to clean up (ie. no onclose,
formdestroy
> > etc), in essence no message seems to be sent to pick up.

> Killed is killed. You don't get notification. If you're writing a
> "terminator" program, it's always best to locate the other program's main
> window and politely send it a WM_CLOSE - if that works, it's much
> cleaner. Under WinNT-family, you can "inject" an ExitProcess call into
> the process (described in Windows Developer's Journal August 1999). If
> you must just "kill" the process, you can expect problems. And if you're
> the process being "killed", there's basically nothing you can do.
> --
> Neil J. Rubenking
> Contributing Technical Editor
> PC Magazine

> I was trying to clean up if someone else killed my app from the process
list
> in task manager.