>>>Here is conceptually what the form does. When the form is opened it processes some data received from an outside source; one record at a time. When all "new" data has been processed, the user gets the message "No More Data to Process" and when he/she clicks on Ok button, the form is released. Therefore, there is a need to release the form after the messagebox. So why is it "so brutal"?
>>>
>>>>It cannot reales at that point because code is still executes in its method. Add RETURN to exit the method.
>>>>I'm curious what kind of form is it that you terminate is so brutally?
>>
>>Dmitry,
>>
>>What I do in that case is call the methods from the form's init. After that, I return FALSE from the form's init.
>>So, I do not have to release the form, since it wasn't "created" ...
>
>I think you are simplifying this. The form has many features and therefore the INIT method of the form has to be "finished" at some point and the form must be "created." Then the "control" goes to various UI controls of the form (textboxes, command buttons, etc.). So the form has to be released somewhere after certain data has been processed.


There's no problem if you put the 'actions' at the end of the form's init() - and then return false

Try it - and you will see