>Hi friends:
>
>Since Starting of Time (at least for me) I designed a form class with a cancel bottom. Its property cancel is set to .T. and it always did what I expect.
>
>I programmed click event with a property for example "secure=.t." for forms where you input lots of information and perhaps press ESC for mistake. The I ask "Are you sure?". If not release() doesn't perform and so it has worked fine.
>
>Since now...
>
>A particulary sensible program for a client of mine - who is habituated to ESC and changes are done - claims because now I oblige him to confirm data. My surprise came because despite I ask Are you sure? Put yes or put not form destroys...
>
>Form doesn't have a big thing. a grid with 4 columns, a confirm button and the class buttom quit.
>
>If i return .F. from when event form unloads even.
>
>If I had to judge for this when a button has cancel property set to .t. form closes anyway and click() event peforms to do any process but not return the control to the form.
>
>But most of my forms has the same characteristic and this doesn't happen.
>
>My system structure is like this:
>
>ACTIVATE MENU mymenu
>
>Menu options are DO FORM myform.
>
>Assuming this has no solution as I pose it, do you have any secure way of prevent user from quit form by mistake?
>
>Thank you.
>
> Héctor
Answering your last question only - adding NODEFAULT in form's QueryUnload method should prevent form's closing.
If it's not broken, fix it until it is.
My Blog