BB>  JW> I read it as 12NOV97.  I use that 971201 format in a computer
BB>  JW> database  as a date code.  YYMMDD will always give you a proper
BB>  JW> chronological order when sorted.
     So, you're the one who will make everything crash
on 000101!
     I can't remember if I told this: I have already
hit the "year 00" problem.  At a computer club meeting,
Tom paid his dues for three years.
     I brought up his record from my data base.  I
normally hit the "0" key to increase a person's
membership by one year.  I hit it once and we went to
"98".  Hit it again and he went to "99".  One more time
and he went to "10"!  That took a little figuring: the
computer logic there was 99 + 1 = 100, then it took
only the first two digits.  I corrected the program
accordingly.
     Then I ran the second program.  This one makes a
list of all who are due or past due and puts it on the
club's BBS.  Anyone a year or more past due is deleted
from the list.  Tom was deleted!  Tom was deleted three
or four times before I got that program corrected.
     When I send out the meeting reminder cards,
"Expires mm/yy" is put above the name.  Those who are
due, or past due, have "Expired mm/yy" in red.  Tom was
included.  It's a WordPerfect macro that does the
addressing.  That's now corrected.
     At the club meeting last week, someone mentioned
the 00 problem and it gave me a chance to say I'd run
into it and it was all Tom's fault.  It least, these
were QuikBasic programs (and WordPerfect macro) I'd
written myself.  I knew how and could correct them!
  FIDO: Bill White @ 1:135/110 (Miami)
 InterNet: bill.white@110.sunshine.com
 * SLMR 2.1a * (A)bort, (R)etry, (H)ug_teddy_bear_and_cry?
--- Maximus 2.01wb
---------------