From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0308_01C764E2.8373F670
Content-Type: text/plain;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

  No "function of Outlook" needed to be fixed.  What you are updating is =
your scheduled events.  This only applies to events you scheduled before =
you updated Windows with the knowledge of the change in DST.  A =
consequence of that is the events you scheduled have the wrong time =
because you changed the meaning of that time.  Despite your trying to =
attribute blame for something you apparently do not understand, Outlook =
still requires no update.  This is why you can update the same scheduled =
events against the Exchange store.  The issue is with the scheduled =
events not the code that uses them.

   As for your last paragraph, I can't guess what you are blabbering on =
about.  You are not making any sense.  My question was simple, why did =
you not attempt any preperation by checking the support site when you =
were well aware and discussed in advance that the government's DST = change
had consequences to software.  It seems you answered this partly = which is
that you didn't care to prepare in which case you deserve what = you get.

Rich

  "Geo."  wrote in message =
news:45f6106b$1{at}w3.nls.net...
  "Rich"  wrote in message news:45f5e849{at}w3.nls.net...

  >>   You are not patching Outlook.  You are updating your existing =
calendar=20
  >> items which if you were using Exchange you could have done by =
running a=20
  >> tool against the Exchange store.<<

  Call it what you like, it is a function of outlook that needed fixed, =
that=20
  function is not available to me via anything but outlook.

  >>   It's still something to do.  Had you looked at the DST Help and =
Support=20
  >> Center on microsoft.com (http://support.microsoft.com/gp/cp_dst) =
you=20
  >> would see this clearly spelled out.  Why did you never look?<<

  Because it never occurred to me that in the dll hell world of MS where =
the=20
  rule is system integration and code reuse even at the cost of extreme=20
  bloating, that they would be so inconsistent as to recode what already =

  exists. Well no wait, that did occur to me, it just wasn't important =
enough=20
  to worry about.

  Geo.=20

------=_NextPart_000_0308_01C764E2.8373F670
Content-Type: text/html;
        charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable








  No "function
of Outlook" needed =
to be=20
fixed.  What you are updating is your scheduled events. 
This = only=20
applies to events you scheduled before you updated Windows with the = knowledge of=20
the change in DST.  A consequence of that is the events you =
scheduled have=20
the wrong time because you changed the meaning of that time.  =
Despite your=20
trying to attribute blame for something you apparently do not = understand,=20
Outlook still requires no update.  This is why you can update the = same=20
scheduled events against the Exchange store.  The issue is with the =

scheduled events not the code that uses them.
 
   As for your last =
paragraph, I can't=20
guess what you are blabbering on about.  You are not making any=20
sense.  My question was simple, why did you not attempt any =
preperation by=20
checking the support site when you were well aware and discussed in = advance that=20
the government's DST change had consequences to software.  It seems = you=20
answered this partly which is that you didn't care to prepare in which = case you=20
deserve what you get.
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45f6106b$1{at}w3.nls.net..."Rich"=20
  <{at}> wrote in message news:45f5e849{at}w3.nls.net...=
>>  =20
  You are not patching Outlook.  You are updating your existing =
calendar=20
  >> items which if you were using Exchange you could have =
done by=20
  running a >> tool against the Exchange =
store.<<Call it=20
  what you like, it is a function of outlook that needed fixed, that=20
  function is not available to me via anything but=20
  outlook.>>   It's
still something to do.  =
Had you=20
  looked at the DST Help and Support >> Center on =
microsoft.com (http://support.microsoft" target="new">http://support.microsoft.=">http://support.microsoft.com/gp/cp_dst">http://support.microsoft.=
com/gp/cp_dst)=20
  you >> would see this clearly spelled
out.  Why did you =
never=20
  look?<<Because it never occurred to me
that in the dll =
hell=20
  world of MS where the rule is system integration and code reuse =
even at=20
  the cost of extreme bloating, that they would be so inconsistent =
as to=20
  recode what already exists. Well no wait, that did occur to me, it =
just=20
  wasn't important enough to worry about.Geo.=20


------=_NextPart_000_0308_01C764E2.8373F670--

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