Infopath form is placed on our own Web Part Page or custom page
That is, the infopath form is embedded in the Web parts page or custom page.
I. Basic knowledge of xmlformview:
Generally, in Moss, the formserver is used to view and fill in the infopath form on a separate Moss page.
If we want to place infopath forms in our own Web Part pages or custom pages, we need a form-loaded container. The xmlformview control is a form web loading container control provided by infopath. We can use xmlformview to load infopaht to custom webpart and custom page.
Xmlformview is a webpart. Therefore, before using xmlformview in Moss, you must deploy xmlformview on the moss website before using xmlformview to load the infopath form on the moss page.
Xmlformview is included in the Microsoft. Office. infopath. server. dll file. The xmlformview class inherits from the webpart class, so it is a webpart. Before use, deploy the xmlformview webpart to Moss.
Ii. xmlformview deployment method:
1) set Microsoft. office. infopath. server. DLL (in the server's c: \ Program Files \ microsoft office servers \ 12.0 \ bin) is copied to the bin directory of the IIS Directory corresponding to the Web application you want to deploy;
2) In the safecontrols section of Web. config, add
<Safecontrol Assembly = "Microsoft. Office. infopath. server, version = 12.0.0.0, culture = neutral, publickeytoken = 71e9bce111e9429c"
Namespace = "Microsoft. Office. infopath. server. Controls" typename = "xmlformview" Safe = "true"/>
3) iisreset, which can be used to export xmlformview Web part from the website.
4) add and activate webpart: Go to the Web part library page of the website set, click "new" on the toolbar to go to the new Web Part Page, and select import Microsoft. office. infopath. server. controls. use the xmlformview component
3. Attributes of xmlformview
Function:
Showheader: display the toolbar above
Showfooter: display the following Toolbar
Editingstatus: Edit status settings: init, closed, edting
Options: parameter. Only the disablesave parameter is supported. Whether to display the parameter settings of the Save button
Data Binding:
Xsnlocation: form template address (for example, http: // MOSS/doclib1/Forms/template. xsn)
Xmllocation: Address of the Form file to be loaded (for example, http: // MOSS/doclib1/Mao. XML)
Savelocation: storage location of the XML file in the filled form (for example, http: // MOSS/doclib1 /)
Showheader: whether to display the top toolbar of xmlformview
Showfooter: whether to display the toolbar at the bottom of xmlformview
Editingstatus: sets the editing status, including init, closed, and editing options. You can set disablesave parameters and set whether to display the Save button.
Xsnlocation: Address of the form template (http: // localhost/doc/Forms/template. xsn)
Xmllocation: Address of the Form file (http: // localhost/DOC)
Savelocation: storage address of the form XML file (http: // localhost/doc/test. XML)
Savelocation is the location of the document library xmllocation is the URL of an XML file in the document library xsnlocation is the location of the form template, if the infopath form is directly published to the document library, the address relative to the address of the document library is like "forms/template. xsn address
This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/xjzdr/archive/2008/06/26/2588487.aspx