When the Microsoft Access ODBC Driver reads a date prior to 1753, the returned date is not consistent with the date actually stored in the database. When you use the Microsoft Access ODBC Driver to write dates prior to 1753, the stored dates when viewed by Microsoft Access are not consistent with the dates written into the database.
↑ Back to the top
The Microsoft Access ODBC Driver is designed to handle dates of 1/1/1753 or later in order to be consistent with Microsoft SQL Server's handling of dates. If the ODBC Driver reads or writes dates prior to 1753, inconsistent results are returned.
↑ Back to the top
A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
The English version of this fix should have the following file attributes or later:
File Name Date Version Size
------------ ---------- ----------- -------
ODBCJT32.DLL 05/22/2000 4.0.6322.00 312,080
↑ Back to the top
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
↑ Back to the top
Microsoft Access allows the storage of date values in the range of 1/1/0000 to 12/31/9999. You can read and write pre-1753 dates by using the Microsoft Access ODBC driver, but the value written or read may not correspond with the actual date stored in the Microsoft Access database. Therefore, reading and writing pre-1753 dates is not supported with the Microsoft Access ODBC Driver unless this hotfix is applied.
After applying this hotfix, the Microsoft Access ODBC Driver will support dates of 1/1/1601 and later.
NOTES:
With Microsoft SQL Server, officially supported dates start from 1/1/1753, which was the year when the Gregorian calendar was standardized. Before 1753, dates may be off.
This hotfix doesn't validate the dates against any particular calendar system (such as Gregorian) for dates before 1753, it simply stores and retrieves the datetime value stored inside the Access database.
↑ Back to the top