From: John Cuccia 

On Sun, 11 Mar 2007 18:40:21 -0700, "Rich"  wrote:

>   I never said or implied that CDO ignores the OS timezone facility.

I confirmed that in the message below.    The inference is mine.

> All you can infer from the KB article which I quoted is that in addition to
the OS, CDO contains some time zone tables.

Actually, I can infer anything I want, and I take "CDO-based
programs...depend on separate internal time zone tables" to mean that
CDO doesn't use the OS timezone tables.

And I think that is ridiculous.

>Rich
>
>  "John Cuccia"  wrote in message
news:0vs8v2la4von7nlj149699sv5luhfsch74{at}4ax.com...
>  Sorry, I didn't mean to put words in your mouth.  What you said,
>  exactly, was
>
>  'The other, according to the KB,
>  http://support.microsoft.com/?kbid=926666, is that "Collaboration Data
>  Objects (CDO)-based programs such as Outlook Web Access depend on
>  separate internal time zone tables" '
>
>  That doesn't change the fact that is indeed stupid for an app or an
>  app framework or object library, or whatever CDO is, to ignore the OS
>  timezone facility.  It created lots of extra work for Exchange admins
>  and for MS developers.
>
>
>  On Sun, 11 Mar 2007 12:55:53 -0700, "Rich"  wrote:
>
>  >   I didn't say this or anything close.  What I mentioned is what is in the
KB article which is that there are some private tables in CDO which affects
CDO clients like OWA.
>  >
>  >Rich
>  >
>  >  "John Cuccia"  wrote in message
news:nmi8v294gnregrd894kk66cmj7as5uflu4{at}4ax.com...
>  >
>  >  Where MS really caused problems is with pieces like Exchange Server
>  >  Outlook Web Access.  As Rich mentioned earlier, it ignores the OS
>  >  timezone definitions and uses its own.
>  >
>  >  That's just stupid.

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