Thank you very much, Sue, this is somewhat as we suspected. However, what
we didn't suspect was that we would have to program the change using code.
We had simply hoped there was a standard Outlook 2007 option for making this
substitution. It would have been nice, given the ability we have to design
forms, if there had been an easy way to substitute our custom forms for the
defaults or for existing forms (including all their current associations).
All this leads to two more questions, if we may?

FIRST, As you indicated, the data is stored separate from the display form.
Therefore, if we add new information fields to a form, how do the new fields
get added to the database?

SECOND, it appears, from the link you emailed, that forms can replace the
default or else be assigned to specific folders, is that correct? If so,
are we better off assigning the new form to separate folders or as the
default?

Thanks,

Richard

****************
"Sue Mosher [MVP-Outlook]" wrote in message
...
There's no need to transfer data, as a form is just a code/UI template. All
the data stays where it is, and you change the value of the MessageClass
property to point to the new published form, e.g. IPM.Contact.MyNewForm. The
page at http://www.outlookcode.com/article.aspx?id=39 has links to scripts
and tools to do this.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Blue Max" wrote in message
...
Once we have designed a new contact form, how do we transfer the data from
the old contact form to the new contact form? Or how do we assign the new
contact form as a default form for displaying and editing the contact
data?