| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Outlook |
From: "Rich"
This is a multi-part message in MIME format.
------=_NextPart_000_035E_01C76AC6.4B80F580
Content-Type: text/plain;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
If you change the time or the time zone Outlook adjusts. The issue =
here was that the time zone definition changed so the times Outlook =
stored before the definition change were not correct after the = definition
change. Only the interval where the definition changed was = affected.
Switching time zones is no issue.
Rich
"Geo." wrote in message =
news:45ffb319$1{at}w3.nls.net...
Yes that's what I was asking, so Outlook does use the system time =
zones, but=20
once used it sticks by what they were when the appointment was =
created,=20
changing system time zones has no effect on existing appointments, =
only=20
future appointments.
This is why you were saying outlook doesn't need to be patched, just =
the=20
existing appointments need to be modified to match the new time zone=20
information. I get it now, thanks.
Geo.
"Rich" wrote in message news:45ff35c6{at}w3.nls.net...
Recurring appts are complex and I can't tell you how they work =
exactly.=20
They do behave as if you repeated a bunch of single appts.
Nothing in Outlook was changed and Outlook will continue to work as =
long=20
as the definition of the time zones does not change again just as it =
worked=20
fine before there was a time zone definition change.
Rich
"Geo." wrote in message =
news:45ff156a$1{at}w3.nls.net...
I was complaining that after the time change a recurring appointment =
showed
as the wrong time for march up until the old time change date even =
though=20
I
had patched my time zones in Windows.
I'm assuming that now that the time zones are patched, if I were to=20
schedule
another recurring appointment it would be correct for the next few =
time
changes.
Geo.
"Rich" wrote in message news:45fea0e3{at}w3.nls.net...
The twice a year EST/EDT change is part of the relationship. =
That it
switches twice a year remains but when it switches between EST and =
EDT
changed. That is the relationship change to which a refer.
I don't know how recurring appts are handled in Outlook. It's =
complex=20
as
you can make changes to either the series or individual events and
everything just works. Ignore these and consider single appts since =
these
are what people were complaining of being off after the government =
DST
change.
Rich
"Geo." wrote in message =
news:45fe6326$1{at}w3.nls.net...
Yes it did, but it that has always been true, it changes twice a =
year as
has
been the case since I created the event in 2000. So you are saying =
when=20
I
created a recurring event in 2000 the system created a thousand =
separate
events and used the EST/EDT standard to do so and now that this =
standard
has
changed some of those events are scheduled for the wrong time and =
so=20
this
is
why a separate patch was required?
So if I go and create a new recurring appointment today, it should =
be
correct and not require a patch because outlook will use the =
corrected
timezone information now?
Geo.
"Rich" wrote in message news:45fd5d8d{at}w3.nls.net...
8 AM in your local time zone is not the same time in UTC every =
day.
The
actual time depends on the relationship between localtime and UTC. =
That
relationship changed.
Rich
------=_NextPart_000_035E_01C76AC6.4B80F580
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
If you
change the time or =
the time=20
zone Outlook adjusts. The issue here was that the time
zone=20 definition changed so the times Outlook stored before the
definition = change were=20
not correct after the definition change. Only the interval where = the=20
definition changed was affected. Switching time zones is no=20
issue.
Rich
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)SEEN-BY: 633/267 5030/786 @PATH: 379/45 1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.