-----Original Message-----
From: Barry A. Watzman <Watzman(a)ibm.net>
To: Discussion re-collecting of classic computers
<classiccmp(a)u.washington.edu>
Date: Wednesday, 6 January 1999 14:42
Subject: Y2K
The problem arises simply because people (programmers
included) normally
write dates in the format >"mm/dd/yy", as in
12/31/99. Not just in computer
programs, but in normal, day-to-day lives. It's that simple, >and that is
all that there is to it.
Only if you live in America. Much of the world (like here, or the UK, New
Zealand etc)
use dd/mm/yy in their "normal, day-to-day lives."
I have personally had numerous headaches with software written (mostly) in
the USA where
this unwarranted assumption on date useage is hard coded into the damn
software.
Accounting packages are prime offenders. So is a well known DOS based Fax
program.
This usually results in users moving to a package that does not make silly
assumptions
about date useage outside America. I know there are 250+ million of you,
but we're not
the 53rd state. (Yet anyway) We "ain't gonna" change the way WE do things
here.
It would make our lives a lot easier if such things were an option, some
authors get it
right, and allow it to be a config option, sadly, lots don't.
Oh, and our financial year is from 1 July to 30 June, not 1 January to 31
December.
Had that trouble as well. Grrrr.
Cheers
Geoff Roberts
Computer Room Internet Cafe
Port Pirie
South Australia.
netcafe(a)pirie.mtx.net.au