No, obviously I don't want invalid data written to the tables. However, the application is currently in VFP 6 and is installed at 100's of customer sites worldwide. In our testing, it turns out that since VFP 6 allowed this, some customers have bad dates in the files. It's on old records, data they don't use. Obviously its not the end of the world for them, the fact that they've been running for years like this w/o problems indicates that. However, if we upgrade them to a new version of our app compiled under 8, it will become a problem as 8 crashes as soon as it accesses the date field. So when they run reports, browse, search, etc. they'll get crashes now. It's just a farily significant change in behavior from 6 to 8 (maybe 7 too, we never used 7)

That said, has anyone run into this? I'll probably contact MS about it to see what they say but I can't find anything on the MS KB so far.

Thanks,
Chris

>>In VFP6: The bad date is written to the table, but does not display in the
>>text box once the text box loses focus.
>>In VFP8: VFP immediately throws a "Date/datetime evaluated to an invalid value"
>>Note that this error does not occur if the text box is unbound.
>>
>>Has anyone else seen this? Any setting to make VFP 8 behave like 6, short of
>>an on error routine to trap the bad date and display a message?
>
>Do I understand correctly that you want invalid data written to your table? If so, may I ask why?