>Hilmar, thanks for the reply.
>
>>May I suggest a different validation strategy. Postpone everything
>>until the record is saved. The user can write any garbage he likes into
>>the TextBoxes, etc., go back, correct it, without any error messages.
>>As soon as he tries to save, he sees a list of rules violated.
>
>>This is much simpler to program. Also, it is more flexible for the end-user.
>
>I agree with you in the case of simple forms, eg. where there is not much dependency of one control upon another. Unfortunately, the form in question has the contents and enabling of some controls depending on the value of others, so validation cannot wait until the form is saved.
>
>Regards,
>Alan
I do this too - enable or disable objects in the LostFocus() Event. But in my systems, validation itself is postponed until the record is saved.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
