![]() |
Time Stamp on Messages
I appear to be missing something with relation to timezones.
I am using CDO to connect to two seperate mailboxes. When I send a message to both of these mailboxes at the same time, the result I get for oMessage.TimeReceived are different by a factor of 7 hours. The strange thing is, I checked in outlook, the received time looks correct for both. I also checked under ToolsOptionsCalender OptionsTime Zone. They are both set to Mountain Standard. Since the script is running on the same machine to connect to these two mailboxes I have ruled out any regional time settings on the local client. Is there somewhere else timezone information is stored for the mailbox? Both mailboxes are on the same exchange server also. |
Time Stamp on Messages
How and when doyou read the property? It is supposed to be stored in the UTC
timezone. Outlook UI and CDO 1.21 (through the Message.ReceivedTime property) convert the value to teh local timezone. -- Dmitry Streblechenko (MVP) http://www.dimastr.com/ OutlookSpy - Outlook, CDO and MAPI Developer Tool - "Bob Smith" wrote in message ... I appear to be missing something with relation to timezones. I am using CDO to connect to two seperate mailboxes. When I send a message to both of these mailboxes at the same time, the result I get for oMessage.TimeReceived are different by a factor of 7 hours. The strange thing is, I checked in outlook, the received time looks correct for both. I also checked under ToolsOptionsCalender OptionsTime Zone. They are both set to Mountain Standard. Since the script is running on the same machine to connect to these two mailboxes I have ruled out any regional time settings on the local client. Is there somewhere else timezone information is stored for the mailbox? Both mailboxes are on the same exchange server also. |
Time Stamp on Messages
Is this CDO 1.21?
If so, the property for time zone may be incorrect. Use Session.SetOption("TimeZone") to set the correct time zone. The setting is stored on the user's mailbox, in property 0x7D020102 on the inbox folder. The time zone is the first DWORD of the property value -- 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 appear to be missing something with relation to timezones. I am using CDO to connect to two seperate mailboxes. When I send a message to both of these mailboxes at the same time, the result I get for oMessage.TimeReceived are different by a factor of 7 hours. The strange thing is, I checked in outlook, the received time looks correct for both. I also checked under ToolsOptionsCalender OptionsTime Zone. They are both set to Mountain Standard. Since the script is running on the same machine to connect to these two mailboxes I have ruled out any regional time settings on the local client. Is there somewhere else timezone information is stored for the mailbox? Both mailboxes are on the same exchange server also. |
Time Stamp on Messages
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. "Bob Smith" wrote: I appear to be missing something with relation to timezones. I am using CDO to connect to two seperate mailboxes. When I send a message to both of these mailboxes at the same time, the result I get for oMessage.TimeReceived are different by a factor of 7 hours. The strange thing is, I checked in outlook, the received time looks correct for both. I also checked under ToolsOptionsCalender OptionsTime Zone. They are both set to Mountain Standard. Since the script is running on the same machine to connect to these two mailboxes I have ruled out any regional time settings on the local client. Is there somewhere else timezone information is stored for the mailbox? Both mailboxes are on the same exchange server also. |
Time Stamp on Messages
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. |
All times are GMT +1. The time now is 07:08 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 2.4.0
Copyright ©2004-2006 OutlookBanter.com