A few weeks ago, I received a high-priority e-mail from a colleague. The purpose of the e-mail was to inquire whether I had made adequate preparations for the Daylight Saving Time Bug. I was asked whether I had installed the appropriate patches and hot fixes. I was asked whether I had updated my disaster recovery plan in light of this new problem.
I was taken aback. I was aware daylight saving time (DST) in the United States was going to be observed differently in 2007. I presumed patches to reflect those new dates would be distributed. I even had spent a few minutes wondering whether it really would affect any of the applications for which I was responsible. But I never thought of it as a bug–or a real problem. After all, the server and client systems I support have little check boxes to adjust automatically for daylight saving time. Wouldn't un-checking that box and then manually adjusting the time on the appropriate date serve as a work-around for the bug? Apparently not. There must be something much bigger going on here–at least according to a lot of the media hype I have been starting to receive.
The Facts
Recommended For You
Want to continue reading?
Become a Free PropertyCasualty360 Digital Reader
Your access to unlimited PropertyCasualty360 content isn’t changing.
Once you are an ALM digital member, you’ll receive:
- Breaking insurance news and analysis, on-site and via our newsletters and custom alerts
- Weekly Insurance Speak podcast featuring exclusive interviews with industry leaders
- Educational webcasts, white papers, and ebooks from industry thought leaders
- Critical converage of the employee benefits and financial advisory markets on our other ALM sites, BenefitsPRO and ThinkAdvisor
Already have an account? Sign In Now
© 2025 ALM Global, LLC, All Rights Reserved. Request academic re-use from www.copyright.com. All other uses, submit a request to [email protected]. For more information visit Asset & Logo Licensing.
