>Al:
>Thank you so very much for taking the time to present such a detailed instruction list.
>I appreciated that, as I'm not an advanced VFP programmer.
>
>I had most of my settings pretty much as you listed them. Nevertheless I did set everything up EXACTLY
>as you specified, and I'm still getting the same result... an EXE that will not die (until I reboot).
>
>All my other apps compile and run (and close) perfectly...without this problem.
>I've compared my form's properties with others I've used, and they match up ok.
>So I'm thinking there has to be something else in that folder that's not allowing this app to die (some setting
>or something else?).
>
>As these things usually turn out... it has to be something really basic...simple.
>
>The only thing that's different in this app from others I've written, is that it had complained ... wanting me to add
>a header file (which I've never used before)... PRO4_app.h (in the OTHER/text files section of the PJX).
>Accordingly, I added #INCLUDE C:\PRO4\PRO4_APP.H to the main.prg
>
>I don't know why it was asking for this, but that's the only difference from previous apps.

Are you saying you created a brand-new project, followed the steps in my last post and it didn't work for you? It was extremely simplified and wouldn't look anything like the app you're trying to work with, but it should have worked properly and shown the concept.

Do you know if you're using any development framework such as ProMatrix, Visual FoxExpress etc.? With some of those products, when they're installed they hook into the VFP IDE. They can then do things like automatically add references, libraries or other components to any projects that are opened in the IDE.

If you are using a framework, in general you *must* do things "the framework way". If you try to fight it you get no end of grief. In that case your best bet by far is to ask on the framework support forum.

Another possibility might be if you have a framework installed and you opened an app that was not originally developed using that framework. The framework might try to do some sort of conversion. Do you recall getting any kind of warning like that?