>> >Probably it will be better to move all validation code to Click event of
>> >Save button. By this way you'll never get in a trap...
>> >
>> >Have a happy day
>> >Vladimir Shevchenko
>> >
>> Completely agree. Valid event is real legacy (I understand that we all hate
>> this word).
>
>My users would disagree. They're quite used to have all their errors
>reported on the spot, before they move off the field. In most cases it's
>not an error message, but a lookup table, messagebox or a popup to
>choose a value from, etc. Moving this to the Save button would mean that
>they have to get several fields back to correct the error.
>
>The worst example of this kind of interface was the M$ bug report form -
>I tried to fill one while I was testing VFP 3.0beta. The form had some
>thirty fields, took several minutes to fill in, and I've skipped some
>fields I considered unimportant. At the final OK button, it said the
>field #2 can't be blank, but didn't put me back there, had to click on
>it and write something. Clicked on OK, got another message, but pressed
>ESC - and all the fields blanked out.
>
>Of course, I didn't submit anything. Just dropped the matter.

Sure. I just want to mention that there is evident difference between DOS-like (where users tab from field to field) and Windows interface where users click by mouse. You and me know that most of users complain moving to Windows, but what can we do with this. Should we accomodate Windows app to DOS-like features? I don't think so. It's better to repeat the phrase "This is Windows Standard" until users will get quiet.