>>Textbox.error would be more appropriate, IMO. Let the beast clean up its own mess :).
>
>Dragan,
>
>Thank you for the tip. As it turns out, textbox.error can't successfully trap it because the error is occurring on our DO FORM line of code. If I put the trapping code in the form's error method then I got it to work. Of course, this is just for one form within our app. I'll have to see if I can apply this to all our forms that contain dateboxes.

Oh no. Another inconsistency. This is a remnant of the ReadError(), where most of the other errors would be caught by On Error, but the error in a date entry would display "invalid date" unless you had On ReadError. Why is this error not passed to the textbox's own error method? I got no idea, but I think it should be. Well, "nobody's perfetc".

You may just add this to the error method in your form class, of course, so you wouldn't have to visit all your forms.