Примери за използване на Browser-compatible form templates на Английски и техните преводи на Български
{-}
-
Colloquial
-
Official
-
Medicine
-
Ecclesiastic
-
Ecclesiastic
-
Computer
Filters are not available in browser-compatible form templates.
Note: Browser-compatible form templates can only run at the Domain or Full Trust security level.
NET languages are supported in browser-compatible form templates.
However, browser-compatible form templates cannot be configured to allow users to submit data to a database.
Master/detail controls are not supported in browser-compatible form templates.
In addition, this article lists the features that are supported in browser-compatible form templates, the features that cannot be used in browser-compatible form templates, andthe differences in behavior that may occur when forms that are based on browser-compatible form templates are viewed in different browsers.
Unlike a default value, placeholder text is not supported in browser-compatible form templates.
InfoPath controls orfeatures that aren't supported in browser-compatible form templates are either hidden or disabled so that you aren't tempted to use them during the design process.
Data connections that submit data to a database are not supported in browser-compatible form templates.
When you select this check box, controls orfeatures that won't work in browser-compatible form templates are either hidden or disabled so that you aren't tempted to use them during the form-design process.
This is because certain controls andfeatures are not supported for use in browser-compatible form templates.
For example, certain InfoPath features are not supported in browser-compatible form templates, and this can lead to problems during the publishing process.
Making the cursor advance automatically to the next control is not supported in browser-compatible form templates.
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.
The following table lists the Office InfoPath 2007 controls that support conditional formatting andwhether they are available for browser-compatible form templates.
The procedure for merging forms in a SharePoint library that are based on browser-compatible form templates is the same as merging forms that users open and fill out in InfoPath.
Developers can use the InfoPath managed code object model to create custom business logic in browser-compatible form templates.
Consequently, you can use InfoPath features in this view that are not supported in browser-compatible form templates, such as user roles or master/detail controls.
The following table lists the Office InfoPath 2007 controls that can be disabled or set to read-only by using conditional formatting andwhether the controls are available for browser-compatible form templates.
If the problem results from an unsupported setting- for example, if your form template specifies user roles,which don't work in browser-compatible form templates- InfoPath displays a more descriptive alert that explains the problem.
The data connection files that are contained in a SharePoint connection library can describe either a Web service connection or a SharePoint library connection, andcan be used in both Filler and browser-compatible form templates.
Similarly, you can design a template part that is destined for use in browser-compatible form templates.
The following table lists the Microsoft Office InfoPath 2007 controls that support data validation andwhether they are available for browser-compatible form templates.
Compatibility problems occur when a form template contains features that are not supported in browser-compatible form templates.
The following table lists the Office InfoPath 2007 controls that support conditional formatting andwhether they are available for browser-compatible form templates.
The ability to use the Verify on server check box in the Design Checker task pane to retrieve server-generated errors andwarnings for template parts that are designed for browser-compatible form templates.
For example, if the original form template included user roles,you will see an error in the Design Checker task pane after you change the compatibility setting because user roles are not supported in browser-compatible form templates.
If you plan to create a browser-compatible form template, keep in mind that the document action bar, which is visible when filling out forms in Microsoft Office documents, including InfoPath forms, is not visible in browser-compatible form templates that users fill out in a Web browser.
When you design a browser-compatible form template, some features, such as the spelling checker, are unavailable for use in InfoPath because they do not work in a Web browser.
In a browser-compatible form template, any InfoPath features, settings, and controls that won't work in a Web browser are hidden or disabled in design mode.