Unfamiliar Outlook fields--need to export them?

[Adam Ruben]

I'm building a feature to export contacts to Excel. My form has 291
properties (including nearly 100 user properties), too many rows for Excel
so I have to cut some. I'm using Outlook 2002. There are many built-in
properties (fields) I've never heard of that seem easy to drop, but I want
to preserve all fields necessary to import this file into a different copy
of Outlook and have it work ok. Can I skip fields like Application, Session,
Outlook Internal Version, Parent, FormDescription, GetInspector,
MessageClass, NoAging, IsConflict, Actions, Saved, Journal, UserCertificate,
UserProperties, and ItemProperties? What about ones that sound like they're
really for mail messages, like conversationIndex, ConversationTopic,
DownloadState, or MarkForDownload?

Also, in exporting, certain fields are hanging up the export routine and
causing errors (e.g. Type Mismatch). For example, ReferredBy, which in the
Locals window shows up as having value <> rather than "" as most text fields
do (same problem with email fields). Or Attachments, which seems to have no
Value property. For these fields do I need some other syntax to export them
than Item.ItemProperties.Item(fieldname).Value?

 

[Sue Mosher [MVP]]

Probably, but you should look up each one in Help to make sure and to understand which are child objects with their own properties.
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers