RSS
The Associated Press warns us all about the dreaded March 11 and April 1 problem...
For three weeks this March and April, Microsoft Corp. warns that users of its calendar programs ''should view any appointments... as suspect until they communicate with all meeting invitees.''Wow, that's sort of jarring -- is something treacherous afoot?
Actually, it's a potential problem in any software that was programmed before a 2005 law decreed that daylight-saving time would start three weeks earlier and end one week later, beginning this year. Congress decided that more early evening daylight would translate into energy savings.
Software created earlier is set to automatically advance its timekeeping by one hour on the first Sunday in April, not the second Sunday in March (that's March 11 this year).
The result is a glitch reminiscent of the Y2K bug, when cataclysmic crashes were feared if computers interpreted the year 2000 as 1900 and couldn't reconcile time appearing to move backward. This bug is much less threatening, but it could cause head-scratching episodes when some computers are an hour off.
Microsoft warns of calendar problem - [via] Link.
To fix all this, download the "Microsoft Office Outlook Tool: Time Zone Data Update Tool for Microsoft Office Outlook" - Link.
This is bad news. Between devices, bios software, and your desktop OS, this is bound to be a nuisance at the very least. (...and I know I'm not the only person in the world who's worked on billing software that needs to accomodate for the time change...)
Daylight savings time is such a bizarre notion in the first place. Why not just mandate that govt. employees come in an hour earlier during part of the year?
Frankly, in a world where it's more and more common to be working with people across the country or around the globe, it seems like we should be thinking about switching to GMT based timekeeping.
Reply to this comment
The die has been cast
Reply to this comment
On Carey Street
Reply to this comment