I read the link you gave, but am still confused. Below you said "Any
custom fields that you want to use in the merge need to be defined for the
folder, not just the form, though."
From this comment, obviously, defining a custom field for the folder is a
different process than defining it for the form. I just do not see where in
the process one does that. In the roughest terms, it seems that the process
goes something like this.
1.. Start with a new, default contact form to use as the basis for your
custom form.
2.. Customize the form to suit your needs.
3.. Publish the form to the Contacts folder.
4.. Set the form as the default form for the Contacts folder by changing
the folder properties.
5.. Set the message class of each item in the folder to the message class
for the new form.
My questions:
1. Are #1-4 pretty accurate (though rough)?
2. How should #5 be reworded to be accurate?
3. Where does "defining the custom fields for the folder, not just the
form" fit in?
Thanks.
2) No. See
http://www.outlookcode.com/d/fields.htm for best practices for
defining fields in folders both with and outside the custom form design
process.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers