From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_01D5_01C76939.1F1BB3B0
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   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

  "Geo."  wrote in message =
news:45fcc3d7$1{at}w3.nls.net...
  "Rich"  wrote in message news:45fab048$1{at}w3.nls.net...
  >>   It's not the time when you created them that is the issue.  It is =
the=20
  >> future time of the scheduled event which before you updated Windows =
for=20
  >> the change in DST was incorrect so the UTC time of the future event =
at=20
  >> the point you scheduled it was incorrect.  Later you changed the =
DST=20
  >> definition the future event still has the same incorrect UTC time =
which=20
  >> when converted to the future local time using the new DST =
definition is=20
  >> off by one hour.<<

  I must not be understanding you, if I schedule an event for 8am every =
day,=20
  should it not be 8am every day including the day after we change the =
time?=20
  This is how it's always worked in the past, time change happens but =
events=20
  still occur at 8am local time. This time when the time changed =
happened I=20
  found my event was scheduled for 9am.

  >>   I can't tell you all the applications that look at Outlook's =
store or=20
  >> their capabilities.  There are many.<<

  I didn't ask you to name them all, I asked for one.

  Geo.

    "Geo."  wrote in message =
news:45fa179b$1{at}w3.nls.net...
    When I set my events, I was GMT-500 which was the correct offset, =
the=20
  other
    day my timezone went to GMT-400 but Outlook didn't compensate, =
instead it
    moved my appointments from 8am to 9am.

    Name one application that will alert me to the events scheduled in =
the
    outlook schedule (without outlook running).

    Geo.

    "Rich"  wrote in message news:45f96221$1{at}w3.nls.net...
       Events tied to local time don't get affected by DST changes.  =
They only
    care that the local time is correct.  The issue with appts in =
Outlook are
    that they are stored in UTC and when you created them the =
relationship
    between local time and UTC was incorrect so the UTC time associated =
with=20
  the
    event is incorrect.  The tool you run fixes these incorrect times.

       There are plenty of applications that look at your Outlook data =
without
    Exchange or you having run Outlook.  I couldn't begin to tell you =
the
    features of all of these.

    Rich


------=_NextPart_000_01D5_01C76939.1F1BB3B0
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   8 AM in
your local time =
zone is not=20
the same time in UTC every day.  The actual time depends on the=20
relationship between localtime and UTC.  That relationship=20
changed.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45fcc3d7$1{at}w3.nls.net..."Rich"=20
  <{at}> wrote in message news:45fab048$1{at}w3.nls.net...=
>>  =20
  It's not the time when you created them that is the issue.  It is =
the=20
  >> future time of the scheduled event which before you =
updated=20
  Windows for >> the change in DST was incorrect so the UTC =
time of=20
  the future event at >> the point you scheduled it was=20
  incorrect.  Later you changed the DST >>
definition the =
future=20
  event still has the same incorrect UTC time which >> when =
converted=20
  to the future local time using the new DST definition is
>> =
off by=20
  one hour.<<I must not be understanding
you, if I =
schedule an=20
  event for 8am every day, should it not be 8am every day including =
the day=20
  after we change the time? This is how it's always worked in the =
past, time=20
  change happens but events still occur at 8am local time. This time =
when=20
  the time changed happened I found my event was scheduled for=20
  9am.>>   I can't tell
you all the applications =
that=20
  look at Outlook's store or >> their
capabilities.  =
There are=20
  many.<<I didn't ask you to name them
all, I asked for=20
  one.Geo. 
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
message news:45fa179b$1{at}w3.nls.net...=
 =20
  When I set my events, I was GMT-500 which was the correct offset, the=20
  other  day my timezone went to GMT-400 but
Outlook didn't =

  compensate, instead it  moved my appointments from 8am to=20
  9am.  Name one application that will alert me to the =
events=20
  scheduled in the  outlook schedule (without outlook=20
  running). 
Geo.  "Rich" <{at}> wrote
in =
message=20
  news:45f96221$1{at}w3.nls.net...=
    =20
  Events tied to local time don't get affected by DST changes.  =
They=20
  only  care that the local time is correct.  The issue =
with appts=20
  in Outlook are  that they are stored in UTC and when you =
created them=20
  the relationship  between local time and UTC was incorrect so =
the UTC=20
  time associated with the  event is
incorrect.  The =
tool you=20
  run fixes these incorrect
times.     There =
are=20
  plenty of applications that look at your Outlook data =
without =20
  Exchange or you having run Outlook.  I couldn't begin to tell you =

  the  features of all of these. =20
Rich

------=_NextPart_000_01D5_01C76939.1F1BB3B0--

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