Sue, in answer to your question, made the comment essentially because we've
rec'd a <few> reports (out of a great many users) where user-defined fields
weren't picked up when the message class changed but unfortunately we didn't
have the luxury of getting the raw data (PST file) to find out why (whether
it's because there was actually a slight name variation or field type
difference or some other potential cause - don't know, just know what we
were told and how the end user was able to get at their data in these
isolated cases. All that CG-MCM (our Message Class Modifier) does (like any
of the other tools which exist that ultimately perform the same function) is
simply change the message class - no more - no less.
Just for the record, we don't recommend exporting unless there's a real good
reason for it even tho we now also sell an export product (as is also
clearly noted on our website and in our Help file for the product). Fully
agree that most of the reasons that people import/export for reasons
described here in the forum can be better accomplished in other ways that
are much better for what they are trying to accomplish.
Karl
__________________________________________________
Karl Timmermans - The Claxton Group
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2003"
http://www.contactgenie.com
Why would you export/import? As long as the new form has the same fields as
the existing contacts, just changing the MessageClass property value on the
existing items should be sufficient.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers