From: "Geo." 

I'm not sure what you mean, I have scheduled events in the system
scheduler, these outlook events are not shown there they are shown only in
Outlook. Scheduled events in the system scheduler were fine, these are
Outlook events and I don't receive notifications of them unless Outlook is
running? If it's a system scheduler why do I not get notification unless
Outlook is running? Is there some other software that will give me
notifications and allow me to change the outlook events besides Outlook?

As to preparation, it's simple, this is a non-critical function for me.
Unlike most MS'ers I don't live and die by a computer scheduler. They are
about as important to me as the local temperature/weather gadget. Does that
bother you?

Geo.


"Rich"  wrote in message news:45f61647$1{at}w3.nls.net...
  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
  >> items which if you were using Exchange you could have done by running a
  >> tool against the Exchange store.<<

  Call it what you like, it is a function of outlook that needed fixed, that
  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
  >> Center on microsoft.com (http://support.microsoft.com/gp/cp_dst) you
  >> 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
  rule is system integration and code reuse even at the cost of extreme
  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
  to worry about.

  Geo.

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