ACC: Synchronization Fails When System Date Is Greater Than 2038

Last reviewed: March 17, 1998
Article ID: Q180081
The information in this article applies to:
  • Microsoft Access versions 7.0, 97

SYMPTOMS

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

When you set the system date on your computer to a year greater than 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 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 2039 to avoid this error.

STATUS

This behavior is by design.

MORE INFORMATION

Setting the system date to a year greater than 2038 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 : OdeGen kb2000
Version : WINDOWS:7.0,97
Platform : WINDOWS
Hardware : x86
Issue type : kbprb
Solution Type : Info_Provided


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 17, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.