Quote:
|
Originally Posted by sven
I don't see any Aussies piping in here. Maybe they feel we haven't a thing to complain about, with just hour differences. Those people have half time zones to deal with. When It's 12 in Sydney it's 11:30 in Adelaide. Sheesh.
|
Don't get me started:
Firstly there's the half hour difference Sven mentioned.
Now we have the crazy situation where Queensland (the State on the north Eastern coast of Australia) doesn't have Daylight Savings Time, but the other Eastern states do. This means people living on the border may have to change their watch when they go to work/school across the border - then back again when they get home. Think of New York having daylight Saving and New Jersey not having it.
Quote:
|
Originally Posted by heov
so everyone knows next year daylight savings time is all messed up. it's like 2wks earlier/later or something.
question: is my phone gonna know that? i assume my pc is covered through windows update or something.
what about my pocket pc?
what about my tv?
next day light savings is gonna be killer 
i can see it now... i manually update my stuff to an hour ahead... then 2wks later when it's programmed to do it, it does it again, and i'm late |
You guys don't know what you're in for with the change to the start/end of DST. It's going to get very ugly.
Let me tell you from experience - we've been through this twice and it creates absolute havoc. The government changed the time zone in 2000 for the Sydney Olympics - we started DST the last Sunday in August instead of the the Sunday in October (remember we're "Down Under" so all our seasons are reversed - summer is Dec-Feb). This meant rolling out a fix for all the Windows computers. Trouble is MS didn't provide the fix till a few weeks before for Windows and not at all for PocketPC.
The effect of the change is that any meeting that is already in your calendar for the period between the new start date and the old date (ie March 11 - April 1, 2007) will move by an hour - that includes recurring meetings. Yes - that's right - all meetings already in the Calendar prior to you applying the patch will be out by one hour. This really annoys people - especially senior managers who show up to meetings an hour late (or is it early - I can't remember).
We did this all over again for the Commonwelath Games in Melbourne in 2006 - although this time they only moved the end of DST by one week. Still painful but not quite so bad.
Let's hope this time - since it actually affects Americans and not just us poor Aussies - Microsoft will release a patch for Windows Mobile (not just Windows).
Then there's the TiVos, Blackberries, PVRs etc that will all need patching. Looks like the DoE has no idea the havoc they're going to cause :-)
I'd like to say I can just sit back and watch the chaos - but I work for a multinational - so I now get to go through the pain for the third time. Maybe I'll dig up the VB code that moves all appointments during the relevent period by an hour - once the change has been implemented.
Good luck - and start preparing now - the sooner you make the change, the fewer appointments you (and if you're an IT person - your users) will have during the affected period.
The problem is caused because Outlook stores all appointment internally in UTC (or GMT) time. It knows how to cope with DST - until you change the definition of DST in the OS. Outlook then gets itself twisted and all appointments in the changed period are out by an hour.
Linear Mode
