Thus, for these systems, Y2K compliance is already a critical issue. Certain cycles, such as fiscal years, will begin in 1999 and end beyond January 1, 2000. Again, date awareness for systems which operate within these cycles is already crucial. However, if the year is evenly divisible by 400, then a leap year is in effect. Systems should continue to handle normal and leap years as they had done in the past, well into the next century.
Many businesses only operate during the week.
If all of these conditions have been satisfied, it is reasonable to assume that the system is Y2K compliant. Due to the tight integration and interoperability of systems nowadays, it is wise to remember the adage that a chain is only as strong as its weakest link. It will undoubtedly be the little things which create the biggest problems.