Year 2000 Compliance

Geoida uses system-derived date values for the date and time of processing as printed in output file headers and job descriptions only. No date-reliant functions are otherwise used in any database functions or operations or during normal data processing.

Where dates are used, all system-derived year values are validated and any prior to 1950 are corrected to the following century (100 years added) on the assumption that these have been derived from 2-digit year values supplied by non-compliant hardware or operating system. Printed date formats (eg report headers) are hard-coded as 4-digit year values, and at no time does Geoida depend upon Windows settings for Short or Long date formats.

Geoida conforms to the Standards Australia definition of Year 2000 Compliance as expressed in the document SAA/SNZ MP77:1998 : A Definition of Year 2000 conformity requirements (Revised November 1998) in which the following rules of compliance are defined …

Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during and after the year 2000. In particular -
Rule 1 - No value for current date will cause any interruption in operation
Rule 2 - Date-based functionality must behave consistently for dates prior to, during and after year 2000
Rule 3 - In all interfaces and data storage, the century in any date must be specified either explicitly or by unambiguous algorithms or inferencing rules
Rule 4 - Year 2000 must be recognised as a leap year in terms of handling both the 29th of February and day 366

Standards Australia Y2K Industry Program

For complete details of SAA/SNZ MP77:1998, refer to SAA/SNZ MP77:1998 - A Definition of Year 2000 conformity requirements

Converted from CHM to HTML with chm2web Standard 2.85 (unicode)