In an old thread "William" posted this in a RATS thread:

Originally posted by William
Just realized... 2012 is the Y2K temporary fix. Rather than recode everything as was initially planned, 2012 is the real year date-reliant software now becomes in trouble. 99% of all Y2K software fixes were relatively simply dial-backs of reference dates.... the simple fix is that any two-digit year-code is assumed to be before 1/1/2012.

Interesting that they picked 2012.

Does anyone have more information on this? is his statement accurate?

this was the first time I have heard a connection between Y2K and 2012.

That doesn't make alot of sense to me why that would be possible. The entire point of the Y2K scare was that alot of legacy systems were developed in an era when memory was precious. The reason for the problem was that many systems only accepted a 00-00-00 date format, and no one knew what would happen when it rolled over. If it wouldn't recognize a date format 1-1-00 why would it recognize 1-1-2012? I've heard highly speculative stuff that there was a fix put in some systems with various dates that would do the Y2K thing on various dates usually the triples and was kind of expecting discusion of one for 08-08-08.

the next one will be Y3K

but in all seriousness, i doubt it will be a problem, funnily enuff i had an issue here at my work for some weird reason all the computers dates had changed they were 2 hours slow (approx) but set to 2013, no one noticed it untill someone tried to set an apointment calendar event in outlook and it kept giving them grief about it.
problem was easily fixed but i found it alittle odd