Acctually, it's very easy to trap it! Just SET NOTIFY OFF (to turn off the default message) and change the ON READERROR to your trapping routine. You know, ON READERROR... old dBase command! :) If you set ON READERROR in GotFocus and restore it in LostFocus, everything is ok. Only that you still cannot get the wrong date value (in case you want to do something with it).

Vlad

>Good point, Vlad. With invalid dates, there is a problem in trying to trap them and control the UI part. The only sure cure I have ever come up with, and it's not an elegant one, is to capture the date in a Character textbox with a mask and then test on LostFocus. Another way is to forget date entry altogether and place calendar control access.