Hi Steve,

I may have to do it that way which will take some time since the form has over 60 objects spread out in three pages. I was trying to avoid doing that.

The thing is, it works fine if I just run it from the command line as in DO FORM , but from the app, it just won't close.

Arriyel

>>Hi Steve,
>>
>>None here. This form used to be a modeless form before we started the latest version of the app. We had to recreate the form almost from scratch since the logic has changed in the data access part (SQL back end from FoxPro DBC).
>>
>>Could it be that it doesn't have any active input fields? I have a logon form that works fine and and entity form that does also. They both have active/enabled input fields.
>>
>
>A form does not need to have input fields. Have you changed the form to modeless for troubleshooting purposes? I suspect the problem will still exist, as there is most likely a dangling object reference somewhere...either inside the form or outside.
>
>You will have to start removing code and functionality until it will release properly, then add stuff back one by one to find the offender.

Speak using soft and sweet words in case you have to eat them later.