Jim-

I generated a quick-and-dirty application using the wizard and example data. I then changed one of the forms to WindowStyle = Modal. I could close the form with the "X" whether I opened it from the QuickStart or the File | Open menu option. Therefore, it would seem that you've added code somewhere in the form that may be keeping it open. You say you do 'THISFORM.Release'...I presume you mean you do it in the QueryUnload()? So, WAG, do you also have some other code in the method?

The way you might want to approach debugging the form is to put a breakpoint at the start of the method code you think should be running when you close the form and trace it.

>I have used the VFP application wizard to create my application. The application includes many forms, and I take advantage of the Quick Start form that the VFP application wizard provides.
>
>Some of the forms in my application have the WindowType property set to 1-Modal. This is because these forms get called by other forms as subroutines. I want the user to close these forms before returning to the calling form.
>
>However, I also want the user to be able to call these forms directly, using the Quick Start dialog.
>
>I have noticed that the modal forms behave properly when called from another form. When the user clicks the Exit button on the form, I execute THISFORM.Release. The form goes away. However, when the form is run from the Quick Start dialog, clicking Exit on the form does not make it go away. It stays on the screen and is active. And, since the form is modal, there is nothing else in the application that I can access.
>
>If I change the WindowType property to 0 - Modeless, the user is able to close the form using the exit button, and return to the Quick Start dialog.
>
>I want to continue using these forms as Modal forms. Any suggestions on how I can get these forms to work with the Quick Start dialog? I have a hunch that the problem lines in the VFP 8 application framework on which I've built the application. I have tried tracing through the code, but it isn't clear to me where the problem lies.
>
>Thanks in advance for your help,
>Jim