Hi Robin,
I think that by the time you get to the destroy event it's too late. Possibly returning .f. will halt destruction but you will probably need to move your code to QueryUnload.
>When the user closes my form I want to run my default class code for the form as if the user wants to save the changes, if the user chooses Yes, I want to validate my fields, if one is not correct I want to prevent the form form closing. If the user chooses No I want to exit but not save. If the user chooses Cancel I want to return to the form.
>
>My code for save,yes no cancel is in my default destroy class for the form
>
>How do I pick up that my default destroy event has returned .f. & stop ny form from closing.
>
>Hope this makes sense.
>
>Rob
Regards,
Mike
"We try to solve the problem by rushing through the design process so that enough time is left at the end to uncover the errors that were made because we rushed through the design process."
- Glenford Myers
If you're going through hell, keep going. - Walt Disney
