In a message dated 1/5/00 5:34:51 PM Eastern Standard Time, [log in to unmask]
writes:

<<  assuming some folks didn't get rid of CALENDAR(), on the hp3000 it will
 be Y28   ;)) >>

I support a manufacturing and purchasing package written in the 1970's
that uses HP's single-integer CALENDAR dates everywhere, in data bases
and files.  The date conversion routines for converting between the internal
CALENDAR dates and MM/DD/YY dates on screens failed at the end of
1999.  Management kept insisting that the date problems did not need to
be fixed because the software would be replaced before it became a
problem.  They insisted right up until the day someone entered a purchase
order with a delivery schedule extending into 2000, and MRP failed.
Now I've fixed that problem, but of course management insists that the dates
don't need to changed to double integers or 8-digit dates because "The
software will be replaced before 2028 becomes a problem."

You're right, Brian, some people will be frantically working on the 2028
problem in about 20 to 25 years.

Cecile Chi