Knowledge Base

ACC: Synchronization Fails When System Date Is Greater Than 2038

Article ID: 180081

Article Last Modified on 1/22/2007

Microsoft Access 95 Standard Edition
Microsoft Access 97 Standard Edition

This article was previously published under Q180081

Moderate: Requires basic macro, coding, and interoperability skills.

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 <file> and replica <file> 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 a Time() function to record events during synchronization. This 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 described in the "Symptoms" section.

RESOLUTION

If you use replication in Microsoft Access, make sure that the system clock is set to a date earlier than the year 2038 to avoid this error.

STATUS

This behavior is by design.

MORE INFORMATION

Setting the system date to a year greater than or equal to 2037 ordinarily does not affect the functionality of Microsoft Access, which 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.

Additional query words: inf prb Y2K Year 2000 replication synch millennium

Keywords: kbprb KB180081