>Not at all! Where'd you get that idea?

I can't remember, may be I didn't wash my hands after some reading… From how you formulated the question, I'm glad you don't suspect me :) Seriously, it seems logical to me that the more dodefault() calls you have to make, the more likely your class design is questionable. I mean, if something is the default, everything else should be an exception.



>FWIW, if valid returns 0 or .F., I think displaying a message that the data isn't valid and can't be saved is perfectly acceptable. If you want, you could offer to discard changes instead, and call the same method as the cancel button.

True, but I thought it will duplicate the Cancel button functionality on the form.

May I ask, how do you handle this, do you have a standard approach?

TIA
dz