This article describes how Microsoft supports integrating Microsoft Business Contact Manager (BCM) with custom solutions.
The level of programmability support for BCM varies, depending on the version of BCM being used. The following sections explain the kind of support that is provided, depending on the version.BCM 2003
BCM 2003 was not designed to be customizable. Although BCM 2003 uses Outlook custom forms itself to implement user interface, Microsoft does not support customizing those forms further by editing the forms in form design mode. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
You cannot customize Business Contact Manager forms in the Outlook forms designer
BCM 2007 provides the ability to add custom fields to records. This is part of the BCM feature set and does not involve customizing the Outlook forms using the Outlook forms designer. For more information on this, please visit the following blog:
For developers, Microsoft has created a guide for the Outlook 2007 version of BCM. To read this guide, visit the following MSDN website:
This guide shows how to use the Outlook object model to automate various tasks in BCM. Microsoft supports integrating with BCM only if it is done within the scope of what is documented in the BCM Developer Guide.BCM 2010
BCM 2010 provides the ability to customize templates and add custom fields to records. This is part of the BCM feature set and does not involve customizing Outlook forms using the Outlook forms designer. For more information on this, please visit the following blog:
Although BCM 2010 provides general usability improvements compared to BCM 2007, the overall architecture of the data that is stored in Outlook is mostly unchanged. The BCM 2007 Developer Guide has not been updated for BCM 2010, however, information in the Developer Guide can be used as a basis for integrating with BCM 2010 and Microsoft will support this scenarios.
Many of the code samples in the Developer Guide contain code samples that reference a particular folder path in BCM 2007. Because the BCM 2010 folders are one level deeper in the folder path, these paths will have to be updated. For example, consider a VBA code sample that has the following line of code:
Set bcmContactsFldr = bcmRootFolder.Folders("Business Contacts")
This code would have to be updated to the following:
Set bcmContactsFldr = bcmRootFolder.Folders("Business Records").Folders("Business Contacts")