>Dear Confused:
>
>>>That's a good example why it's not healthy practice to use
>>Control.Valid
>>events. IMHO, the right solution is to move all validations to
>>cmdSave.Click event.
>>
>>Ed, this certainly solves the problem of avoiding the Valid clause for
>>certain key-strokes. Unfortunately most of my clients want validation
>>before they leave the field, not for all fields as they try to save
>>the
>>data. Does your scheme allow for this?
>>
>>Confused in California
>
>Simple! Save the changes after each field!
Thanks, Paul ;-) I gather your users never want an Undo button?
Barbara
