|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
May 23rd 07, 05:18 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
ContactItem Help Clarification
The ContactItem Class in Outlook is a beautiful and powerful thing.
I'm curious: How does Outlook actually store the contact data, for example, with respect to: BusinessAddress BusinessAddressCity BusinessAddressPostalCode BusinessAddressState BusinessAddressStreet etc. Is the info stored a) unparsed in BusinessAddress or b) parsed in each of the component parts, or c) redunantly, in both. The help has the following remark: Remarks This property is parsed from the BusinessAddress property, but may be changed or entered independently should it be parsed incorrectly. Note that any such changes or entries to this property will be overwritten by any subsequent changes or entries to the BusinessAddress property ---------------------------------------------------------------------- I think this means that the address is ONLY stored unparsed in BusinessAddress, and the components are parsed from that into City, State, etc. I'm curious because I know that Microsoft would have made that decision carefully, and knowing how they made it might help me design unrelated database tables containing addresses. I would take less space to store only unparsed BusinessAddress, but most databases (in my experiences) aren't organized that way. Thanks in advance for your insight. George 
|
| Ads |
|
#2
May 23rd 07, 08:25 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
ContactItem Help Clarification
c) Both. You can see this clearly with the Outlook Spy and MFCMAPI.exe tools.
-- Sue Mosher, Outlook MVP Author of Configuring Microsoft Outlook 2003 http://www.turtleflock.com/olconfig/index.htm and Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "George" wrote in message ... The ContactItem Class in Outlook is a beautiful and powerful thing. I'm curious: How does Outlook actually store the contact data, for example, with respect to: BusinessAddress BusinessAddressCity BusinessAddressPostalCode BusinessAddressState BusinessAddressStreet etc. Is the info stored a) unparsed in BusinessAddress or b) parsed in each of the component parts, or c) redunantly, in both. The help has the following remark: Remarks This property is parsed from the BusinessAddress property, but may be changed or entered independently should it be parsed incorrectly. Note that any such changes or entries to this property will be overwritten by any subsequent changes or entries to the BusinessAddress property ---------------------------------------------------------------------- I think this means that the address is ONLY stored unparsed in BusinessAddress, and the components are parsed from that into City, State, etc. I'm curious because I know that Microsoft would have made that decision carefully, and knowing how they made it might help me design unrelated database tables containing addresses. I would take less space to store only unparsed BusinessAddress, but most databases (in my experiences) aren't organized that way. Thanks in advance for your insight. George
|
|
#3
May 23rd 07, 09:14 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
ContactItem Help Clarification
Thank you.
That surprised me. Does that mean that the entire ContactItem is stored as one big flat record? "Sue Mosher [MVP-Outlook]" wrote: c) Both. You can see this clearly with the Outlook Spy and MFCMAPI.exe tools. -- Sue Mosher, Outlook MVP Author of Configuring Microsoft Outlook 2003 http://www.turtleflock.com/olconfig/index.htm and Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "George" wrote in message ... The ContactItem Class in Outlook is a beautiful and powerful thing. I'm curious: How does Outlook actually store the contact data, for example, with respect to: BusinessAddress BusinessAddressCity BusinessAddressPostalCode BusinessAddressState BusinessAddressStreet etc. Is the info stored a) unparsed in BusinessAddress or b) parsed in each of the component parts, or c) redunantly, in both. The help has the following remark: Remarks This property is parsed from the BusinessAddress property, but may be changed or entered independently should it be parsed incorrectly. Note that any such changes or entries to this property will be overwritten by any subsequent changes or entries to the BusinessAddress property ---------------------------------------------------------------------- I think this means that the address is ONLY stored unparsed in BusinessAddress, and the components are parsed from that into City, State, etc. I'm curious because I know that Microsoft would have made that decision carefully, and knowing how they made it might help me design unrelated database tables containing addresses. I would take less space to store only unparsed BusinessAddress, but most databases (in my experiences) aren't organized that way. Thanks in advance for your insight. George
|
|
#4
May 23rd 07, 10:47 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
ContactItem Help Clarification
It is dangerous to make analogies between Outlook and databases, because you can lose a lot of the key Outlook concepts in the process. For example, Outlook data is semi-structured, in that a folder not only can hold nonhomogeneous items but can have situations where some items are similar in most of their properties, but differ in the custom properties they contain. Better to think of it in terms of object and properties, some of those properties being objects with their own properties (such as Recipients and Attachments). I strongly recommend getting one of the tools I mentioned if you want to explore these concepts further.
-- Sue Mosher, Outlook MVP Author of Configuring Microsoft Outlook 2003 http://www.turtleflock.com/olconfig/index.htm and Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "George" wrote in message ... Thank you. That surprised me. Does that mean that the entire ContactItem is stored as one big flat record? "Sue Mosher [MVP-Outlook]" wrote: c) Both. You can see this clearly with the Outlook Spy and MFCMAPI.exe tools. "George" wrote in message ... The ContactItem Class in Outlook is a beautiful and powerful thing. I'm curious: How does Outlook actually store the contact data, for example, with respect to: BusinessAddress BusinessAddressCity BusinessAddressPostalCode BusinessAddressState BusinessAddressStreet etc. Is the info stored a) unparsed in BusinessAddress or b) parsed in each of the component parts, or c) redunantly, in both. The help has the following remark: Remarks This property is parsed from the BusinessAddress property, but may be changed or entered independently should it be parsed incorrectly. Note that any such changes or entries to this property will be overwritten by any subsequent changes or entries to the BusinessAddress property ---------------------------------------------------------------------- I think this means that the address is ONLY stored unparsed in BusinessAddress, and the components are parsed from that into City, State, etc. I'm curious because I know that Microsoft would have made that decision carefully, and knowing how they made it might help me design unrelated database tables containing addresses. I would take less space to store only unparsed BusinessAddress, but most databases (in my experiences) aren't organized that way. Thanks in advance for your insight. George
|
|
#5
May 24th 07, 01:51 PM
posted to microsoft.public.outlook.program_vba
|
|||
|
|||
|
ContactItem Help Clarification
Thank you.
Will do. "Sue Mosher [MVP-Outlook]" wrote: It is dangerous to make analogies between Outlook and databases, because you can lose a lot of the key Outlook concepts in the process. For example, Outlook data is semi-structured, in that a folder not only can hold nonhomogeneous items but can have situations where some items are similar in most of their properties, but differ in the custom properties they contain. Better to think of it in terms of object and properties, some of those properties being objects with their own properties (such as Recipients and Attachments). I strongly recommend getting one of the tools I mentioned if you want to explore these concepts further. -- Sue Mosher, Outlook MVP Author of Configuring Microsoft Outlook 2003 http://www.turtleflock.com/olconfig/index.htm and Microsoft Outlook Programming - Jumpstart for Administrators, Power Users, and Developers http://www.outlookcode.com/jumpstart.aspx "George" wrote in message ... Thank you. That surprised me. Does that mean that the entire ContactItem is stored as one big flat record? "Sue Mosher [MVP-Outlook]" wrote: c) Both. You can see this clearly with the Outlook Spy and MFCMAPI.exe tools. "George" wrote in message ... The ContactItem Class in Outlook is a beautiful and powerful thing. I'm curious: How does Outlook actually store the contact data, for example, with respect to: BusinessAddress BusinessAddressCity BusinessAddressPostalCode BusinessAddressState BusinessAddressStreet etc. Is the info stored a) unparsed in BusinessAddress or b) parsed in each of the component parts, or c) redunantly, in both. The help has the following remark: Remarks This property is parsed from the BusinessAddress property, but may be changed or entered independently should it be parsed incorrectly. Note that any such changes or entries to this property will be overwritten by any subsequent changes or entries to the BusinessAddress property ---------------------------------------------------------------------- I think this means that the address is ONLY stored unparsed in BusinessAddress, and the components are parsed from that into City, State, etc. I'm curious because I know that Microsoft would have made that decision carefully, and knowing how they made it might help me design unrelated database tables containing addresses. I would take less space to store only unparsed BusinessAddress, but most databases (in my experiences) aren't organized that way. Thanks in advance for your insight. George
|
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| contactitem - how can I add comment text | SwissMiss | Outlook and VBA | 3 | January 24th 07 05:14 PM |
| ContactItem.Save() | Virda | Outlook and VBA | 9 | January 10th 07 12:27 PM |
| Junk Email filter Clarification | Bartly | Outlook - Installation | 0 | July 18th 06 07:57 PM |
| All Day Event reminders-a clarification | ClareNC | Outlook - Calandaring | 1 | July 5th 06 04:34 PM |
| New ContactItem with same EntryID | jim | Add-ins for Outlook | 3 | January 20th 06 08:01 PM |
Linear Mode
