>Dragan
>I have tried set notify off, this error seems to be beyond all vfp code. I started playing with my dateTextBox class a bit. If I put a textBox on a form with the same properties only, there is not a problem. There is something in my class code that is causing the vfp invalid date error to fire before any events such as valid, lostFocus etc. or any other code that does not allow me to capture the error
>
>I copied all the set commands you suggested except for strictDate which I like set at 1, no luck. If I put in a a year such as 6 or 61 or 6111 or 6110, it is fine, if I put in 611 or 211 as the year, it blows. I haven't verified it yet, but any and only 3 digit year entries seem to cause the problem
>
>I find the behavior in my aforementioned practice date field. If I put a date in such as 51/02/06, it just sits there and does not move to the next field. I'll keep playin' with it and let you know if

Three digit years are taken seriously, i.e. as if you've preceded them with a zero. So 611 means 0611, which is out of range - which is year 1000 through 9999 for VFP.

Why does that behave differently than 51st of february (or 2nd of 21st month), I have no idea.