Everyone Had a Y2K Compliance
Statement -- Here's Ours!
TC&M is pleased to report we
have completed our "Y-to-K" compliance review on-time and on-budget. We
have gone through every line of code in every program in every system. We have
analyzed all databases, all data files, including backups and historic archives, and
modified all data to reflect the change.
We are proud to report that we have completed the "Y-to-K" date change mission,
and have now implemented all changes to all programs and all data to reflect the new
standards: Januark, Februark, March, April, Mak, June, Julk, August, September, October,
November, December. As well as: Sundak, Mondak, Tuesdak, Wednesdak, Thursdak,
Fridak, Saturdak.
To be honest, none of this "Y-to-K' problem has made any sense to us here. But
we understand it is a global problem, and our team is glad to help in any way possible.
What does the year 2000 have to do with it? Speaking of which, what do you
think we ought to do next year when the two digit year rolls over from 99 to 00?