ACC2002: Synchronization Fails When System Date Is Greater Than 2038 (295173)
The information in this article applies to:
This article was previously published under Q295173 This article applies only to a Microsoft Access database (.mdb).
Moderate: Requires basic macro, coding, and interoperability skills.
For a Microsoft Access 2000 version of this article, see 203627.
SYMPTOMS
When you set the system date on your computer to a year greater than or
equal to 2038, you may receive the following error message:
Synchronization between replica <FileName> and replica <FileName> failed.
The Microsoft Jet database engine could not read the system clock on your computer.
The synchronization then fails without any data being exchanged.
CAUSE
Microsoft Jet replication calls the Time() function to record events during synchronization. The function uses a fixed range of year values. The upper limit of this range is 2038. Dates greater than or equal to 2038 cause the error message that is mentioned in the "Symptoms" section of this article.
RESOLUTION
To avoid this error message when you use replication in Microsoft Access, make sure that the system clock is set to a date earlier than the year 2038.
MORE INFORMATION
With non-replicated Access databases, setting the system date to a year greater than or equal to 2038 generally does not affect the functionality of Microsoft Access. Access can store and work with date values up to December 31, 9999. This error occurs only when the Microsoft Jet database engine records synchronization events.
| Modification Type: | Major | Last Reviewed: | 9/25/2003 |
|---|
| Keywords: | kberrmsg kbprb KB295173 |
|---|
|