>I think I have found the culprit. I was only opening and then closing the application. The app would then hang in memory with the CPU going to max. In the app I have a "Always on Bottom", maximized, and borderless form that is always open (called in the main program) to provide a working area. Within this form is a pageframe and then a number of controls present. I tried the app without calling the form -- quit fine. So culprit is form (or more precisely, something on form). I have a couple of ActiveX controls on the form (most stock Windows, but one is a commercial one). I eliminated the activexs to determine the offending one -- it was a listview control. I am getting an update to the control that will hopefully fix the problem; if not, then I will have to find a work-around or eliminate the control.
>
>Right now I will keep the control anonymous as the vendor has advertised on the UT. Thanks again for your input. It is interesting that the form is being "released" as reported by the objref program but that the activex is most likely being held in memory. I may try several workarounds if the updated control exhibits the same behavior. Right now I am putting the control on the form at design time -- I might try at run-time (via a class) and then explicitly remove the control.
>
>At any rate I will post the results of the control and VFP 9's interaction so others can benefit.

I hope you'll get it resolved soon.