Hi Randy,

You could try is sending a WM_NCDESTROY ( = 0x0082) message via SendMessage, to see if that closes it. I've found this this sometimes does the trick when WM_CLOSE and WM_QUIT don't function, e.g. on Win2K Shell Explorer windows. It's just a shot in the dark, but when it works, it seems to be clean and easy.

Mike

>I am using an ActiveX control in my program that doesn't terminate properly when released. It's not a VFP problem - the same thing happens using the control under VB6 using the vendor's own sample files. So far no help from them other than that they designed it this way. I CAN end it by going into Task Manager and ending the process. What I want to do is incorporate this in my program so that when my program ends it also kills this rogue task. Which API call should be used for this, and can it be used under VFP?
>
> Thanks,
> Randy