There are five criteria a piece of software has to meet
for year 2000 compliance.
The software will operate without error relating to date data.
Sorts must be correct for dates from the same or different centuries.
Calculations on dates must be correct for dates from the same or
different centuries.
The software will not abnormally end or provide invalid or incorrect
results due to date data, especially between centuries.
All calculations for time-related data, such as dates, duration,
days between dates, date of week, will produce the expected results
for all valid date values within the applications.
For any date element represented without century, the correct century is
unambiguous for all manipulations involving that element.
The meaning of dates presented in reports and screens must be unambiguous.
Van Mierlo Software Consultancy certifies the following:
Data files are correctly sorted on dates, even if the data files are from
different centuries.
DAx runs correctly with dates greater than 31/12/1999.
Date based calculations in DAx will run correctly both before
and after the year 2000. The year 2000 is recognised as a leap year.
The only date based calculations in DAx happen when DAx
determines whether or not a new data list needs to be created.
DAx uses the Windows settings to determine how dates are represented.
This may mean that dates use only two digits to indicate the year. In this
case, DAx will assume that dates with years smaller than 50 are in the 21st
century.
DAx uses the Windows settings to determine how dates are represented.
It is up to the user to select a Windows date format that is unambiguous.
