The bomb is still ticking as of 01/01/1900greenspun.com : LUSENET : TimeBomb 2000 (Y2000) : One Thread
The bomb is still ticking. I found out yesterday that a Visual Basic date formatted to #01/03/2000# is going into a database field as #01/03/1900#! With four-digit years throughout, the company certified the application to be Y2K compliant in early 1999. It all looks OK until the user runs a report.
I expect accountants to be burning the midnight oil all over the world as they try to close their January books!
-- Slobby Don (firstname.lastname@example.org), January 05, 2000