From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_00E6_01C767A0.AED63290
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

   It's not the time when you created them that is the issue.  It is the =
future time of the scheduled event which before you updated Windows for =
the change in DST was incorrect so the UTC time of the future event at =
the point you scheduled it was incorrect.  Later you changed the DST =
definition the future event still has the same incorrect UTC time which =
when converted to the future local time using the new DST definition is =
off by one hour.

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

Rich

  "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 =
other=20
  day my timezone went to GMT-400 but Outlook didn't compensate, instead =
it=20
  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=20
  care that the local time is correct.  The issue with appts in Outlook =
are=20
  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 the=20
  event is incorrect.  The tool you run fixes these incorrect times.

     There are 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=20
  features of all of these.

  Rich


------=_NextPart_000_00E6_01C767A0.AED63290
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








   It's not
the time when you =
created=20
them that is the issue.  It is the future time of the scheduled =
event which=20
before you updated Windows for the change in DST was incorrect so the = UTC time=20
of the future event at the point you scheduled it was incorrect. 
= Later you=20
changed the DST definition the future event still has the same incorrect = UTC=20
time which when converted to the future local time using the new DST = definition=20
is off by one hour.
 
   I can't
tell you all the =
applications=20
that look at Outlook's store or their capabilities.  There are=20
many.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45fa179b$1{at}w3.nls.net...When=20
  I set my events, I was GMT-500 which was the correct offset, the other =
day=20
  my timezone went to GMT-400 but Outlook didn't compensate, instead it=20
  moved my appointments from 8am to 9am.Name
one application =
that=20
  will alert me to the events scheduled in the outlook schedule =
(without=20
  outlook
running).Geo."Rich"
<{at}> wrote in message =
news:45f96221$1{at}w3.nls.net...=
  =20
  Events tied to local time don't get affected by DST changes.  =
They only=20
  care that the local time is correct.  The issue with appts in =
Outlook=20
  are that they are stored in UTC and when you created them the =
relationship=20
  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=20
  times.   There are plenty of
applications that look =
at your=20
  Outlook data without Exchange or you having run Outlook.  I =
couldn't=20
  begin to tell you the features of all of=20
these.Rich

------=_NextPart_000_00E6_01C767A0.AED63290--

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