When you design your form template, you can choose to create a form template that can be opened or filled out in either InfoPath or a Web browser. If the form template can be opened and filled out by using a browser, then it is called a browser-compatible form template (browser-compatible form template: A form template that is designed in InfoPath by using a specific compatibility mode. A browser-compatible form template can be browser-enabled when it is published to a server running InfoPath Forms Services.). This type of form template can then be browser-enabled (browser-enabled form template: A browser-compatible form template that has been published to a server running InfoPath Forms Services, and that has been browser-enabled so that users can both display and fill out the form in a Web browser.) when it is published to a server running InfoPath Forms Services.
This article describes how to choose a compatibility setting for a form template, either when you first create the form template or after you have already created the form template. If you're not sure of the current compatibility setting for your form template, you can refer to the Compatibility area on the InfoPath status bar, which is located in the bottom right corner of the InfoPath window.
All form templates are compatible with InfoPath — that is, users can open and edit the forms in InfoPath, provided that the users have InfoPath installed on their computers.
If you have access to a server running InfoPath Forms Services, you can design a single form template that accommodates two kinds of users — those who have InfoPath installed on their computers and those who do not. In the latter case, users fill out forms in a supported Web browser, not in InfoPath. If your users have InfoPath installed, they can open the form in InfoPath and they can experience the full range of form features. Users filling out the form in a browser have access to a more limited set of features, but benefit from being able to use the form even though they do not have InfoPath installed on their computers. If you plan to publish your form template to a server running InfoPath Forms Services, you must keep these limitations in mind.
The process for designing a browser-compatible form template includes specifying a compatibility setting, either up-front, when you first create the form template, or later, while designing the form template. After you design a browser-compatible form template, you can test, publish, and browser-enable it so that users can fill it out in a browser.
In the Design a Form dialog box, you can choose to enable only browser-compatible features for use in your form template. If you do this, InfoPath controls or features that aren't supported in browser-compatible form templates are either hidden or disabled so that you aren't tempted to use them in your form template.
A new form template opens in InfoPath. In the lower right-hand corner of the of the InfoPath window, in the status bar, the words Compatibility: InfoPath and InfoPath Forms Services appear so that you know that the form template will work in a Web browser as well as in InfoPath.
If a feature isn't supported on a server running InfoPath Forms Services, that feature appears dimmed in the user interface and you will not be able to add it to your form template. Similarly, if a particular control isn't supported, it does not appear in the Controls task pane.
You can change the current compatibility setting for an existing form template at any point during the design process. For example, if you inherited a regular, InfoPath-only form template from a coworker, and you now want it to be browser-compatible, you can change the existing compatibility settings for the form template.
An InfoPath-only form template may contain features that are not supported in browser-compatible form templates, such as user roles, custom task panes, or master-detail controls. After you specify new compatibility settings, you can view a list of compatibility problems that resulted from switching the setting in the Design Checker task pane.
Note In some cases, you may see an error when you attempt to change compatibility settings. For example, if you have used Information Rights Management (IRM) to restrict permission to an existing form template, you must remove that setting before you can successfully change the compatibility settings.
The Design Checker task pane will now display errors and messages that resulted from changing the compatibility settings.
The following table describes the difference between errors and messages in the Design Checker task pane.
|Error||The form template will not function correctly. You should fix the errors before you publish the form template.|
|Message||The form template may not function as expected. Messages are less serious than errors. You can choose whether to address the messages before you publish the form template.|
Note If you don't fix the errors, you can still publish the browser-compatible form template to a server running InfoPath Forms Services. However, you won't be able to browser-enable the form template on the server, which means that people cannot display or fill out the form in a Web browser.