Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

ACC2000: Operational Range for Dates in Microsoft Access 2000


View products that this article applies to.

This article was previously published under Q240246
Moderate: Requires basic macro, coding, and interoperability skills.

This article applies only to a Microsoft Access database (.mdb).

↑ Back to the top


Summary

You can store date values in a Microsoft Jet 4.0 database starting with the year 100 and up to the year 9999. However, many database functions support only a limited range of dates. This article describes the operational date range for a Jet 4.0 database.

↑ Back to the top


More information

The low end of the operational date range for Jet 4.0 is the year 200, and the high end of the operational date range is the year 2038. Although you can enter dates with years outside of this range, some Jet functionality will return incorrect results. Non-native Jet database formats, particularly ODBC sources, may or may not support dates outside of the range of Jet 4.0. When dates outside of the range are not supported, imports and exports may fail, records containing dates outside of the specified range may be deleted, or incorrect results may be returned from queries for dates outside of the specified range.

Also, replication limits the low end of the range to the year 200 in order to correctly calculate retention periods and to provide date stamps for certain system tables when the current year is 2000 or greater.

NOTE: The date limits in an Access project are different from those described for a Jet database. Date and time data types for representing the date and time of day in SQL Server 7.0 are:
  • datetime -- date and time data from January 1, 1753, to December 31, 9999.
  • smalldatetime -- date and time data from January 1, 1900, to June 6, 2079.
SQL Server rejects all values it cannot recognize as dates between 1753 and 9999.

↑ Back to the top


Keywords: KB240246, kbinfo

↑ Back to the top

Article Info
Article ID : 240246
Revision : 2
Created on : 6/30/2004
Published on : 6/30/2004
Exists online : False
Views : 273