Need a book? Engineering books recommendations...

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

RE: Y2K Issue

[Subject Prev][Subject Next][Thread Prev][Thread Next]
I have tried this with my computer and the dates are correctly indicated
above the year 1999. As I stated before, the problem stems from older
databases, such as accounting and financial records that use the last two
digits for the year and ignore the century.
The real problem will not be noticed by most until the year 2050 or beyond.
The only problem will be the interpretation of the year in large databases
where the century is ignored.
This can be rectified, but the cost attached to updated the millions or
billions of records saved since the first tape mainframe units is
The majority of our community does not have to worry about this problem. The
large companies such as aerospace industries may have some problems and most
certainly does the Federal and State governments.

Dennis Wish PE

|-----Original Message-----
|From: John O'Brien [mailto:jobrien(--nospam--at)]
|Sent: Sunday, March 01, 1998 9:42 AM
|To: seaoc(--nospam--at)
|Subject: Re: Y2K Issue
|Is there really a problem?   Can't the computor clock be set ahead to see
|what the effect will be?
|> From: Dennis S. Wish <wish(--nospam--at)>
|> To: seaoc(--nospam--at)
|> Subject: RE: Y2K Issue
|> Date: Saturday, February 28, 1998 12:07 PM
|> It is my understanding that this problem will only effect systems that
|> 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
|> issue and is generally not applicable to PC owners since older machines
|> bioses) tend to become extinct and replaced with new bioses or bios
|> upgrades.
|> 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
|> problem due to the structure of the database used - this is why
|> 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
|> operating
|> |>systems, CAD and structural design program vendors intend to address
|> |>"millenium bug"?
|> |>
|> |>Charlie Canitz, PE
|> |>Bel Air, MD
|> |>
|> |Bank of America has sent out questionaires on the Y2K problem potential
|> |small business owners. I have no idea how it may effect CAD systems but
|> know
|> |that all my self written tech spread sheets should not have problems. We
|> are
|> |stictly on pc's but our Novell network server software may be
|> In
|> |addition to that our bookkeeping is done with Quicken which we can
|> |compartmentalize datewise to preclude problems. Would imagine that the
|> firms
|> |utilizing larger micros and mainframe systems will have most to fear
|> |Y2K. External accounting is our largest area of vulnerability(ie:
|> |,receivables , checking and savings accounts etc).
|> |
|> |
|> |
|> |
|> |