Year 2000 Compliance
Finally, even though we are well past 1 January 2000, everyone must remember
that just because a system was brought up to date and was y2k-compliant
on 1 January 2000, that does not mean one cannot install a non-y2k compliant
program after that date. We will all have to be diligent in our continued
efforts to ensure our systems remain y2k-complaint. Many software
products written before 1995, and even some after 1995, are not 2000-ready.
This means that they are unable to handle the date requirements of the
year 2000. This means that if you enter “00” as a date, most software programs
understand this to be 1900, not 2000. Software must be modified or upgraded
to accept 4-digit dates and users must be educated to use 4-digit dates.
Remember, applications must be designed to be 2000-ready and your programmers
must design them as such. Since the only thing stopping programmers from
writing non-2000 ready software today is you, make sure they are writing
2000-ready software. While we will help our customers with this testing
and identifying potential y2k problems, we are not responsible for identifying,
considering, or correcting any Year 2000 deficiency or issues in any of
your systems, or systems with which you interface, or software delivered
by us.