On 12/29/2017 12:17 PM, Mr. Man-wai Chang wrote:
BTW,Â*Y2KÂ*problemÂ*backÂ*thenÂ*didn'tÂ*createÂ*an yÂ*majorÂ*chaosÂ*as.

I wrote an accounting application in 1992 to 2005 and Y2K was an issue
to us. Minor, but probably not as bad as some companies. Our dates
were stored as # of days since 1760 I believe. So 1999 was day 239 and
2000 was just one more 240.

The real issue was display and user input. We stupidly programmed the
engine to just assume 19xx years. How were we to think of 2000 when
the engine was developed back in 1970 or so. Anyway we had to apply a
30/70 rule to dates that 12/31/17, 17 was less than 30 years in the
future so thus it was 20xx, but 12/31/90 was greater than 30 years thus
19xx. And we had to create a special format for MM/DD/YYYY as we
always only displayed 2 digit years.

The application was written in a 4GL proprietary code and was
interpreted by the engine thus no real applications had to be changed
except where users demanded the 4 digit year.

Boy those were the days. Months of testing for such a simple one more
day in the life of humans. :-)