From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0294_01C7641C.878DD670
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   You can infer what you want but it doesn't mean it is supported by =
the statement from which you made the inference.  If you look at the of =
the copies of CDO you might see that it contains references to the Win32 =
API GetTimeZoneInformation from which you can infer and supports that =
your inference is incorrect.

Rich

  "John Cuccia"  wrote in message =
news:9sg9v21tnnr509e6o15qca7equ9534ut6g{at}4ax.com...
  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=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_0294_01C7641C.878DD670
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   You can
infer what you =
want but it=20
doesn't mean it is supported by the statement from which you made the=20
inference.  If you look at the of the copies of CDO you might see
= that it=20
contains references to the Win32 API GetTimeZoneInformation from which = you can=20
infer and supports that your inference is incorrect.
 
Rich
 

  "John Cuccia" <jcuccia{at}bigfoot.com>">mailto:jcuccia{at}bigfoot.com">jcuccia{at}bigfoot.com>
wrote =
in message=20
  news:9sg9v21tnnr=
509e6o15qca7equ9534ut6g{at}4ax.com...On=20
  Sun, 11 Mar 2007 18:40:21 -0700, "Rich" <{at}>=20
  wrote:>   I never said or
implied that CDO =
ignores the OS=20
  timezone facility.I confirmed that in the message=20
  below.    The inference is
mine.> All you =
can infer=20
  from the KB article which I quoted is that in addition to the OS, CDO =
contains=20
  some time zone tables.Actually, I can infer anything I want, =
and I=20
  take "CDO-basedprograms...depend on separate internal time zone =
tables" to=20
  mean thatCDO doesn't use the OS timezone
tables.And I =
think that=20
  is
ridiculous.>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...> =20
  Sorry, I didn't mean to put words in your mouth.  What you=20
  said,>  exactly,
was>>  'The other, =
according=20
  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 Data>  Objects
(CDO)-based programs =
such as=20
  Outlook Web Access depend on>  separate
internal time zone =
tables"=20
  '>>  That doesn't change the
fact that is indeed =
stupid for=20
  an app or an>  app framework or object library, or =
whatever CDO=20
  is, to ignore the OS>  timezone
facility.  It created =
lots of=20
  extra work for Exchange admins>  and for MS=20
 
developers.>>> 
On Sun, 11 Mar 2007 12:55:53 =
-0700,=20
  "Rich" <{at}>
wrote:>> 
>   I =
didn't say=20
  this or anything close.  What I mentioned is what is in the KB =
article=20
  which is that there are some private tables in CDO which affects CDO =
clients=20
  like OWA.> 
>> 
>Rich> =20
  >>  >  "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...> =20
  >     
>  >  Where MS =
really=20
  caused problems is with pieces like Exchange Server>  =
> =20
  Outlook Web Access.  As Rich mentioned earlier, it ignores the=20
  OS>  >  timezone definitions
and uses its =
own. =20
  >  >> 
>  That's just=20
stupid.

------=_NextPart_000_0294_01C7641C.878DD670--

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