Investigating Date Errors
/>
Q
I am migrating a
Microsoft Access application to SQL Server, and
I am experiencing a problem moving the data over
successfully. Is there anything in particular
that I should be looking for when I troubleshoot
this?
A
/>One common problem is that Access supports
dates beginning from January 1, 100, and
Microsoft Visual FoxPro permits dates from
January 1, 1, whereas SQL Server supports dates
from January 1, 1753.
You might not
think that dates prior to January 1, 1753 exist
in your application, but it's easy to make
mistakes during the data-entry process that can
create dates that are valid in Access and Visual
FoxPro but invalid in SQL Server. A typing error
can easily turn May 12, 1990 into May 12, 199 or
May 12, 190. This could be the source of your
problem.