Unfortunately, I'm not familiar enough about the specifics of the 2000
issue, but I do know that it is considered by our corporation to be a
truly BIG deal!
Much of the software that resides on our corporate network is relatively
new (Windows 95 or later) and those programs are not expected to have
problems with the millenium date. But OLDER programs, many of which were
written for mainframe uses that are still very much a part of some of our
data bases -- and those of some of the vendors who serve our company --
must be evaluated for potential problems when 1/1/2000 arrives.
Because many corporations are dependent upon outside resources for many
of their functions and services, it becomes a much bigger problem than
simply looking at one's own software and hardware to determine your
ability to get through the transition to 2000.
In addition to the many private programming experts who can offer
credible advise/support on this issue, there appears to be a growing
number of "public" services who can offer at least some credible info on
what to look for and how to go about determining the extent of the
problem you may encounter.
Hope this helps. Pete