Neither of those are valid time zone values. The maximum possible valid
value is CdoTmzMax = 52. Anything above that is invalid and caused by
corruption of some sort.

CDO uses the property value in the first DWORD of 0x7D020102 for the CDO
time zone. It can become corrupted if accesses are made from another time
zone, if the Windows time zone struct from the registry doesn't match the
MAPI time zone settings or for a number of other reasons. Outlook doesn't
use the CDO value, so it can be correct while the CDO values aren't.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Bob Smith" wrote in message
...
I think I found the answer

objSession.GetOption("TimeZone") = 16386 on the mailbox that exhibits the
incorrect behaviour. Does anyone know what 15385 would be and how that
would
be set on a mailbox. I know how to set it to 12 from a script, but would
like
to know what would case this.