Year 2000 Compliancy Statement

After careful review and evaluation, it is declared that all software product releases published by Vista Software as of July 1st, 1999 are in complete compliance with Year 2000 date storage and analysis requirements. While earlier releases of these products may also be compliant, we cannot certify them as such.

All date field values managed by Apollo, Apollo Database and Artemis are, and have always been, stored in fully-qualified, century-included format (i.e. CCYYMMDD) within the database files and indexes. The SIx Driver RDD v3.02 for Clipper 5.2x is also fully Y2K compliant in all standard tests.

The SetCentury method can be used to force the default display of century values in data-aware controls. Please see the Apollo documentation for specific information. Artemis contains similar API functions -- sx_SetEpoch and sx_SetCentury. Please see the Artemis documentation for additional notes on these functions and their usage. For more on Borland Delphi and/or C++Builder Y2K compliance, visit http://www.borland.com/about/y2000/.

Borland's Delphi and C++Builder products were not fully Y2K compliant, as used by Apollo, until their respective 4.0 releases. In those 4.0 releases, a new TwoDigitYearCenturyWindow variable was declared in the SysUtils unit that is now utilized by Apollo's Epoch property and SetEpoch method. This allows Apollo to predictably make an accurate century determination when only the last two year digits are specified.

While Apollo does also support Delphi 3.x and C++Builder 3.x, if Y2K compatibility is a concern for you and/or your application, you will want to be sure upgrade to the 4.x release or later of Delphi/C++Builder, as well as the most recent release of Apollo.