From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_02F2_01C76A52.9448A5C0
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   Recurring appts are complex and I can't tell you how they work =
exactly.  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 as the definition of the time zones does not change again just as = it
worked 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=20
  as the wrong time for march up until the old time change date even =
though I=20
  had patched my time zones in Windows.

  I'm assuming that now that the time zones are patched, if I were to =
schedule=20
  another recurring appointment it would be correct for the next few =
time=20
  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=20
  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 as=20
  you can make changes to either the series or individual events and=20
  everything just works.  Ignore these and consider single appts since =
these=20
  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=20
  has
    been the case since I created the event in 2000. So you are saying =
when 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=20
  has
    changed some of those events are scheduled for the wrong time and so =
this=20
  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.=20
  The
    actual time depends on the relationship between localtime and UTC.  =
That
    relationship changed.

    Rich


------=_NextPart_000_02F2_01C76A52.9448A5C0
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   Recurring
appts are =
complex and I=20
can't tell you how they work exactly.  They do behave as if you =
repeated a=20
bunch of single appts.
 
   Nothing
in Outlook was =
changed and=20
Outlook will continue to work as long as the definition of the time = zones does=20
not change again just as it worked fine before there was a time zone = definition=20
change.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45ff156a$1{at}w3.nls.net...I was=20
  complaining that after the time change a recurring appointment showed =
as=20
  the wrong time for march up until the old time change date even though =
I=20
  had patched my time zones in Windows.I'm
assuming that now =
that=20
  the time zones are patched, if I were to schedule another =
recurring=20
  appointment it would be correct for the next few time=20
 
changes.Geo."Rich"
<{at}> wrote in message news:45fea0e3{at}w3.nls.net...&nbs=
p; =20
  The twice a year EST/EDT change is part of the relationship.  =
That it=20
  switches twice a year remains but when it switches between EST and =
EDT=20
  changed.  That is the relationship change to which a=20
  refer.   I don't know how recurring
appts are =
handled in=20
  Outlook.  It's complex as you can make changes to either the =
series=20
  or individual events and everything just works.  Ignore these =
and=20
  consider single appts since these are what people were complaining =
of=20
  being off after the government DST
change.Rich  =
"Geo."=20
  <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote =
in message=20
  news:45fe6326$1{at}w3.nls.net...=
 =20
  Yes it did, but it that has always been true, it changes twice a year =
as=20
  has  been the case since I created the event
in 2000. So =
you are=20
  saying when I  created a recurring event in 2000 the system =
created a=20
  thousand separate  events and used the EST/EDT standard to do =
so and=20
  now that this standard has  changed some of
those events =
are=20
  scheduled for the wrong time and so this is  why a =
separate patch=20
  was required?  So if I go and create a new recurring =
appointment=20
  today, it should be  correct and not require a patch because =
outlook=20
  will use the corrected  timezone information =
now? =20
  Geo.  "Rich"
<{at}> wrote in message news:45fd5d8d{at}w3.nls.net...&nbs=
p;   =20
  8 AM in your local time zone is not the same time in UTC every day.=20
  The  actual time depends on the relationship between =
localtime=20
  and UTC.  That  relationship
changed. =20
Rich

------=_NextPart_000_02F2_01C76A52.9448A5C0--

--- BBBS/NT v4.01 Flag-5