![]() | |||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||
|
Y2KPosted 10/7/1998By Carl Miller, AAM Y2K affects the computerized world. It actually seems redundant to use the phrase "computerized world" since it seems that almost everything is computerized in our world now. A significant portion of computerized equipment contains programming chips that read only the last two digits of a year for dates, such as "96" for 1996. Since earlier computers had much less memory, this two-digit system was seen as a way to save storage space within computer memory. While we can easily say in hindsight that Y2K should have been a foreseen problem, software programmers in the 1970s and early 1980s weren't too concerned about potential quirks in their programs 20 to 30 years in the future; besides, what is important now is simply dealing with the problem. Since many programs currently only read two digits for years, they could mistake the date "00" to be the year 1900 when it is intended to refer to the year 2000. A friend recently reported to me that his new credit card with a "00" expiration date wouldn't work at a self-service gasoline pump. The station attendant couldn't take his card because the station's equipment had yet to be upgraded to accept expiration dates beyond 1999. This could be a real problem for travelers planning to use their cards for purchases. Many shop owners will have to make some changes. In our shop, I discovered that my old shop management software was not Y2K compatible. I also had to upgrade my Windows program to complete the changeover. Several shop owners I've talked to use software purchased from companies that are out of business, and the software isn't Y2K compatible. These shops could hire computer programmers to resolve the situation, but a safer method might be to get a whole new system. Most shops should be able to avert any major problems with simple software adjustments or upgrades - at least pertaining to internal operations. But what is somewhat out of the hands of shops owners are the possible outcomes of their year 2000 transactions with other businesses - some of which might not have prepared properly for the situation. It is a good idea to check with your suppliers and bank to find out if their systems are Y2K ready. Some financial experts suggest that you should prepare for an interruption of some business transactions for as long as 60 days. They also recommend that you keep good paper trails in case questions do arise from your financial institution concerning transactions. How well the government handles Y2K is also extremely important. In my state, programmers are working long hours to get the state system ready for the year 2000. Government agencies are working hard, but it's always wise to be somewhat skeptical of the effectiveness of their compliance efforts.
As we near the end of this year, I'm sure you will hear many horror stories about what will happen when the clock hits midnight on Dec. 31, 1999. Predictions for what will happen range from "minor inconvenience" to "severe economic collapse." I have faith that America will come through the year 2000 without a major catastrophe, and preparation is the best thing we can do to avoid problems in our day-to-day business operations. Don't wait until "after the fact" to assess Y2K and the effect it could have on your business. Act today!
|
||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||