Capabilities Not Supported by Form Managers

For performance reasons, the following features aren't supported by the default form manager but may be supported by custom form managers:

• A hierarchy that enables forms to be grouped or categorized within a form library. A form library is essentially a flat-file database of forms.
• Access control for categories of forms, corresponding to message classes or superclasses.
• Support for multiple language versions of the same form in a single form library.

These are entirely implementation issues. There is nothing to prevent a custom form manager from implementing these features.

The MAPI form architecture does not support multiple form managers running concurrently. Although MAPI supports multiple concurrent message store providers, transport providers, and address book providers, only a single form manager is supported.

Because only one form manager may be running at once, if you implement a custom form manager you will have to re-implement any functionality from the default form manager that you need. Since your custom form manager will entirely replace the default form manager, capabilities of the default form manager will be unavailable unless they are duplicated in your custom form manager.