Extracting Form Files

InfoPath form templates are saved as XSN files that encapsulate all the different components of an InfoPath form, including the form’s design, styling, and scripting. While having a single file makes it easy to develop and distribute InfoPath forms, sometimes you will want to view or edit the individual files that make up an InfoPath form. In order to separate these files, you need to extract the form files from your XSN file.

xx xxxxxxx xxx xxxx xxxxx xxxx xx xxxxxxxx xxxx, xxxx xxx xxxx xx xxxxxx xxxx xxx xxxx xxxxxx xxxx | xxxxxxx xxxx xxxxx xx xxxx xxx xxxxxx xxx xxxxx xx xxx xxxxxxxxx xxxxxxxxxxxx.

You can use this dialog box to select a folder in which the extracted form files will be saved or you can click the Make New Folder button in the lower-left corner to create a new folder to hold the form files. An InfoPath form can be made up of a number of different types of files. For example, Table 11-1 lists and describes the files that were used to create the sample Employee Details form.

Table 11-1: A Set of Files Extracted from a Typical Form

xxxxxxxx	Description
xxxxxxxx.xxx	A manifest file generated by InfoPath that contains information about the different components that make up an InfoPath form
xxxxxxxx.xxx	The XML Schema for the form you have created
xxxxxxxxxx.xxx	An XML file containing the sample data to be used with your form
xxxxxxxx.xxx	An XML file containing the template for the default data to be displayed when you create a new form
xxxxx.xxx	The style sheet that will be used to transform the data to create View1 within the form

xx xxxxxxxx xx xxx xxxxx xxxxxx xx xxxxx xxxx, xxx xxx xxxx xxxx xxxxx xxxxx xx xxxxx, xxxxxxxxx xx xxx xxxxxxxxxx xx xxxx xxxx. xxx xxxxxxx, xx xxx xxx xxxxxxxx xx xxxx xxx xx xxxx xxxx, xxxxx xxxxx (xxx, xxx, xxx xx xx) xxxxx xxxx xx xxxxxxxxx.

Also, referring to Chapter 10, in which you looked at scripting, if you are using scripting in your form, you may also have JS or VBS files, which hold either JScript or VBScript code. In addition, you may also have dynamic link libraries (DLLs) or executables (EXEs) that are used to extend InfoPath functionality.

xxxx xxxx xxx xxxx xxxxxxx xxxxx xxxxxx xxxxx, xxxxxxxxx xxx xxxxxxxxxxxxx xxxxx, xxx xxxxxxxxxx xxxxx xx xxx xxxxxxxx xxxxxxx (xxxx xx xxxx xxxxx xxx xxx xxxx xxxx, xxxxx xxxxx xxxxx, xxx xx xxxxx).