impossible
for the computer to tell the difference between a day in 1905 and 2005. Microsoft’s
products,
that assume the year from these short dates, will be updated in 1997 to make it easier to
assume
a 2000-based year. As a result, Microsoft recommends that by the end of the century, all
PC
software be upgraded to versions from 1997 or later."
(Microsoft, p. 1)
PRODUCT NAME
DATE LIMIT
DATE FORMAT
Microsoft Access 95
1999
assumed "yy" dates
Microsoft Access 95
9999
long dates ("yyyy")
Microsoft Access (next version)
2029
assumed "yy" dates
Microsoft Excel 95
2019
assumed "yy" dates
Microsoft Excel 95
2078
long dates ("yyyy")
Microsoft Excel (next version)
2029
assumed "yy" dates
Microsoft Excel (next version)
9999
long dates ("yyyy")
Microsoft Project 95
2049
32 bits
Microsoft SQL Server
9999
"datetime"
MS-DOS(r) file system (FAT16)
2099
16 bits
Visual C++(r) (4.x) runtime library
2036
32 bits
Visual FoxPro
9999
long dates ("yyyy")
Windows 3.x file system (FAT16)
2099
16 bits
Windows 95 file system (FAT16)
2099
16 bits
Windows 95 file system (FAT32)
2108
32 bits
Windows 95 runtime library (WIN32)
2099
16 bits
Windows for Workgroups (FAT16)
2099
16 bits
Windows NT file system (FAT16)
2099
16 bits
Windows NT file system (NTFS)
future centuries
64 bits
Windows NT runtime library (WIN32)
2099
16 bits
Microsoft further states that its development tools and database management systems
provide
the flexibility for the user to represent dates in many different ways. Proper training of
developers to use date formats that accommodate the transition to the year 2000 is of the
utmost
importance. For informational purposes, I have included a chart that represents the more
popular Microsoft products, their date limits, and date formats. (Chart on previous page)
(Microsoft, p. 3)
So . . . is everyone affected? Apparently not. In speaking with the owners of St. John
Valley Communications, an Internet-Access provider based in Fort Kent, they are eagerly
awaiting the coming of 2000. They, Alan Susee and Dawn Martin had enough foresight to make
sure that when they purchased their equipment and related software, that it would all be
year
2000 compliant. It can be done, as evidenced by this industrious couple of individuals.
The key
is to get informed and to stay informed. Effect the changes you can now, and look to
remedy the
one’s that you can’t. The year 2000 will be a shocker and thriller for many businesses,
but St.
John Valley Communications seem to have it under control and are holding their partry hats
in
one hand and the mouse in the other.
As is obviously clear from the information presented, Yk2 is a problem to be reckoned
with. The wide ranging systems (OS) and software on the market lend credence to the idea
that
a "silver bullet" fix is a pipe dream in the extreme. This is not however, an
insurmountable
problem. Efficient training and design is needed, as well as a multitude of man-hours to
effect
the "repairs" needed to quell the ramifications and repercussions that will
inevitably occur
without intervention from within. The sit back and wait for a cure-all approach will not
work,
nor is it even imaginable that some people (IS people) with advanced knowledge to the
contrary,
would buy into this propaganda of slow technological death. To misquote an old adage,
"The
time for action was 10 years ago." Whatever may happen, January 1, 2000 will be a
very
interesting time for some, a relief for others . . . and a cyanide capsule for the
"slackers." What
will you do now that you are better "informed?" Hopefully you will effect the
necessary "repairs
and pass the word to the others who may be taking this a little too lightly. It may not be
a matter
of life or death, but it sure as heck could mean your job and financial future.WORKS CITEDElgan, Mike. "Experts bemoan the denial of "2000 bug"."
Http://www.cnn.com/2000. ( 31 October 1996).Jager, Peter de. "DOOMSDAY." Http://www.year2000.com/doom
(2 November 1996).
* " Believe me it’s real ! Early Warning." Http://www.year2000.com
(4 November 1996).
* " Biting the Silver Bullet." Http://www.year2000.com/bullet
(2 November 1996).Shufelt, Ursula. "Yk2." Ursula@maine.maine.edu. ( 7 November 1996).Duvall, Jed. "The year 2000 does not compute." Http://www.cnn.com/news
(3 November 1996).ITAA. "The Year 2000 Software Conversion: Issues and Observations."
Http://www.itaa.org/yr2000-1.htm ( 7 November 1996).Seligman, James & Issa, Nabil. "The Year 2000 Issue: Implications for Public
Health Information and Surveillance Systems."
Http://www.cdc.gov/year2000.htm (9 November 1996).Microsoft. "Implications of the Year 2000 on Microsoft Products."
Http://army.mil/army-yk2/articles/y2k.htm (9 November 1996).