Appointment time Outlook / WM6.1

[Tom]

Overview: appointments *created* before daylight savings created for
days *after* daylight savings come into effect are showing an hour
out.

I have Outlook 2003 (SP3) and WM6.1 (running on a HTC Touch HD phone)
linking through AS4.5.
The PC system, Outlook Calendar settings and the WM6.1 phone are ALL
set to GMT with automatic daylight saving.

The current date is the 26th March 2009 - three days before the
daylight savings kick in (Sunday 29th).
When I create an appointment in Outlook for any day on or after
Sunday, the time is showing on the phone one hour earlier than it
should. Any appointment before Sunday appears correctly - and as a
test, an appointment in November 2009 appears correctly as daylight
savings will have turned off by then.

I'll only know on Sunday if creating a new appointment shows correctly
on the phone.

I've even tried running the "Time Zone Data Update Tool for Microsoft
Office Outlook", but as I suspected beforehand, it didn't make any
difference.

Can anybody suggest a reason why those appointments are appearing an
hour out?

 

[Sven]

You know, with all the trouble this causes MS, you would think they would
just have DST abolished worldwide. They have the power, don't they? I hope
so.

 

[Tom]

news:[email protected]...

Thanks for the response Todd... as I suspected, I don't think there is
anything that can be done about it.
If anybody knows different, I'd love to hear your theories.

You know, with all the trouble this causes MS, you would think they would
just have DST abolished worldwide. They have the power, don't they? I hope
so.

That's one option... but the first thing they could do is abolish the
US's use of the mm/dd/yyyy date format used by... erm, only the
US!! ;-)
(Ok, so there are actually 8 countries - according to Wiki - but there
are a darn sight more that don't... http://en.wikipedia.org/wiki/Calendar_date)

Tom

 

[Brian Tillman [MVP - Outlook]]

Thanks for the response Todd... as I suspected, I don't think there is
anything that can be done about it.
If anybody knows different, I'd love to hear your theories.

In the majority of cases, the problem is because or more of the devices does
not contain the 2007 DST changes.

 

[Tom]

In the majority of cases, the problem is because or more of the devices does
not contain the 2007 DST changes.

Thanks for the response Brian,

I've only had the phone a couple of months - and it's only existed for
about 6/8 months (I believe), so I would have hoped it was already
"patched". However, I've downloaded and installed KB949168* and it's
still not working correctly.
The KB article does mention specific locations around the world, of
which the UK (running at GMT+0) isn't one of them, so I'm not
surprised the update did nothing.

I'm just amazed that what seems like an obvious problem hasn't been
addressed.
Still willing to conceed if I've got a setting wrong, but other than
setting the time zone (and automatic DST) on the PC (XP)/Outlook 2003
(SP3)/WM6.1 I've run out of ideas.

KB949168 = http://www.microsoft.com/downloads/details.aspx?FamilyId=0D6FC192-3142-4473-B435-B514E4B360A5

Tom

 

[Sven]

I have to say there seems to have been a substantial increase in the
apparently DST related issues over the last year or two. We had a whole
bunch for a while, originally just folks not recognizing their PPC or PC
wasn't on the right TZ because they just set the time and forgot about it.
Then there were a bunch that came up when MS decided to change the way they
offered the options, just time zones and variations on these, rather than
specific cities to choose, at the same time moving the location of the TZ
data from the registry to somewhere. Then there was a spate of problems when
many governments around the world decided that the populace wasn't irritated
enough, they needed to change when DST happens. This last bunch appears to
me to be tied to the real acceptance of converged devices. We know have
carriers deciding what the Time and TZ is on our phones, sometimes that
works well, and sometimes I think they help screw it up. Not sure if it has
anything to do with this particular problem, just a history supporting my
Quixote quest to eliminate DST altogether...everywhere.

In the majority of cases, the problem is because or more of the devices
does
not contain the 2007 DST changes.

Thanks for the response Brian,

I've only had the phone a couple of months - and it's only existed for
about 6/8 months (I believe), so I would have hoped it was already
"patched". However, I've downloaded and installed KB949168* and it's
still not working correctly.
The KB article does mention specific locations around the world, of
which the UK (running at GMT+0) isn't one of them, so I'm not
surprised the update did nothing.

I'm just amazed that what seems like an obvious problem hasn't been
addressed.
Still willing to conceed if I've got a setting wrong, but other than
setting the time zone (and automatic DST) on the PC (XP)/Outlook 2003
(SP3)/WM6.1 I've run out of ideas.

KB949168 =
http://www.microsoft.com/downloads/details.aspx?FamilyId=0D6FC192-3142-4473-B435-B514E4B360A5

Tom

 

[Tom]

I have to say there seems to have been a substantial increase in the
apparently DST related issues over the last year or two. We had a whole
bunch for a while, originally just folks not recognizing their PPC or PC
wasn't on the right TZ because they just set the time and forgot about it.
Then there were a bunch that came up when MS decided to change the way they
offered the options, just time zones and variations on these, rather than
specific cities to choose, at the same time moving the location of the TZ
data from the registry to somewhere. Then there was a spate of problems when
many governments around the world decided that the populace wasn't irritated
enough, they needed to change when DST happens. This last bunch appears to
me to be tied to the real acceptance of converged devices. We know have
carriers deciding what the Time and TZ is on our phones, sometimes that
works well, and sometimes I think they help screw it up. Not sure if it has
anything to do with this particular problem, just a history supporting my
Quixote quest to eliminate DST altogether...everywhere.

Well, after the time changed happened on Sunday - I'm pleased to say
that those appointment that were created in Outlook are now showing up
as the correct time... which is a relief.

New appointments made now are also appearing correctly. The thing
that is now confusing me is that creating a test appointment for
November is *also* showing correctly... I would have expected it to
have been an hour out in the other direction. I hate computers!

Tom