From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_024E_01C7640C.B94B8D70
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   I never said or implied that CDO ignores the OS timezone facility.  =
All you can infer from the KB article which I quoted is that in addition =
to the OS, CDO contains some time zone tables.

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=3D926666, 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...
  >     =20
  >  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. =20
  >
  >  That's just stupid.
------=_NextPart_000_024E_01C7640C.B94B8D70
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   I never
said or implied =
that CDO=20
ignores the OS timezone facility.  All you can infer from the KB =
article=20
which I quoted is that in addition to the OS, CDO contains some time = zone=20
tables.
 
Rich
 

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

------=_NextPart_000_024E_01C7640C.B94B8D70--

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