Need a book? Engineering books recommendations...

Return to index: [Subject] [Thread] [Date] [Author]

RE: Y2K Issue

[Subject Prev][Subject Next][Thread Prev][Thread Next]
It is my understanding that this problem will only effect systems that rely
upon retrieving older, archived databases which did not account for dates
past 12/31/99. The ability to distinguish dates past the year 2000 is a bios
issue and is generally not applicable to PC owners since older machines (old
bioses) tend to become extinct and replaced with new bioses or bios
As far as CAD files are concerned, most of these are bios dependent and
should not pose a problem to an office networked from current equipment.
Information created on older main frames and stored on tape may be another
problem due to the structure of the database used - this is why accounting
systems are so vulnerable. They often require retrieval of older records
which do not conform to a four place year but are limited to the last two
digits (i.e., 98,99,00).
Dennis Wish PE

|-----Original Message-----
|From: Norb Volny [mailto:volnyeng(--nospam--at)COINET.COM]
|Sent: Saturday, February 28, 1998 11:34 AM
|To: seaoc(--nospam--at)
|Subject: Re: Y2K Issue
|>With the year 2000 rapidly approaching, is anyone aware of how the
|>systems, CAD and structural design program vendors intend to address the
|>"millenium bug"?
|>Charlie Canitz, PE
|>Bel Air, MD
|Bank of America has sent out questionaires on the Y2K problem potential to
|small business owners. I have no idea how it may effect CAD systems but
|that all my self written tech spread sheets should not have problems. We
|stictly on pc's but our Novell network server software may be vulnerable.
|addition to that our bookkeeping is done with Quicken which we can
|compartmentalize datewise to preclude problems. Would imagine that the
|utilizing larger micros and mainframe systems will have most to fear from
|Y2K. External accounting is our largest area of vulnerability(ie: billing
|,receivables , checking and savings accounts etc).