Francisco
I migrated almost all my .dbf's to Sql Server and I have been aware of this problem for some time .. I usually put a valid _DateCHk() function on my date fields to make sure this sort of thing doesn't happen .. .dbf does not care if you save a date like 04/25/0207, but Sql Server will throw up a run-time error breaking the application.
The reason this came back on my radar is that I am currently upgrading a huge app that is using dbf\cdx to Sql Server and I am dealing with lots of invalid dates that I am having to fix and account for.
Thanks for your confirmation.
RIik LIpkin
↧