SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Politics : Ask Michael Burke -- Ignore unavailable to you. Want to Upgrade?

To: gnuman who wrote (61929)6/10/1999 9:00:00 AM
From: BGR  Read Replies (1) | Respond to of 132070
 
Gene,

The Y2K problem has to do with any and all date comparisons, as long as one of the dates being compared is past 12/31/99 which would lead to a buffer overflow. It has got nothing to do with the current date per se.

-BGR.




To: gnuman who wrote (61929)6/10/1999 11:54:00 AM
From: benwood  Respond to of 132070
 
BTW, you may already have experienced some Y2K problems and not realized it. There are actually a variety of Y2K dates that come up this year and next, and Jan 1, 1999 was the first as mentioned before. Interestingly, my company's payroll had errors on the first and second checks of the year, on virtually every check issued. Of course, they didn't want to start mass hysteria, so they didn't attribute the problems to anything in particular...


HomeMailHotSubjectMarksPeopleMarksKeepersSettings
Terms Of UseContact UsCopyright/IP PolicyPrivacy PolicyAbout UsFAQAdvertise on SI
© 2026 Knight Sac Media.  Data provided by Twelve Data, Alpha Vantage, and CityFALCON News