Y2K

Year 2000 Conformity of HTS software

The generally accepted definition of year 2000 conformance is:

Year 2000 conformity shall mean that neither performance nor functionality is affected by dates prior to, during and after the year 2000.

The latest versions of HTS's software systems pass the following tests:

From	To	Reason to check
31st December 1998	1st January 1998	existing functionality unchanged
27th February 1999	28th February 1999	existing functionality unchanged
28th February 1999	1st March 1999	existing functionality unchanged
31st August 1999	1st September 1999	first time xx/9/99 is encountered
8th September 1999	9th September 1999	the 9/9/99 problem does not exist
9th September 1999	10th September 1999	the 9/9/99 problem does not exist
31st December 1999	1st January 2000	first time 00 is encountered
27th February 2000	28th February 2000	existing functionality unchanged
28th February 2000	29th February 2000	that 2000 is recognised as a leap year
29th February 2000	1st March 2000	that 2000 is recognised as a leap year
31st December 2000	1st January 2001	the changeover of year from 00 to 01
28th February 2001	1st March 2001	that leap year recognition works for years beyond 2000
28th February 2004	29th February 2004	that leap year recognition works for years beyond 2000
29th February 2004	1st March 2004	that leap year recognition works for years beyond 2000

Additionally the products properly display and import/export all dates.

HTS uses Omnis7 and Oracle7 as the basis for its software systems. Further information may be obtained from the vendors websites