More on the continuing saga of Daylight Savings Time...

Obviously the media is finally starting to figure out that this could be a bit of an issue that unfortunately our legislative representatives were not very "bright" about:

(AP) -- 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

It never ceases to amaze me how our government never bothers to think thru the consequences of something that everyone admits was lobbied by organizations such as candy makers because Halloween would be better. Pour some sugar on this issue...as I predict some people are going to end up bitter before this one is over...