X hits on this document





11 / 47

Microsoft Office 2003 Editions: Overview of Developer TechnologiesSeptember 2004

InfoPath enforces the validity of the captured information according to the schema. The result of information captured in InfoPath is an XML file in the format of the custom XML schema; InfoPath has no special file format. You can only use one schema as the basis for a form.

When designing a form from a custom schema, InfoPath provides suggested controls based on the data type specified by the schema, e.g. a single line text control is suggested for the XSD string type; a date control is suggested for the XSD date type.

When InfoPath forms save captured information as XML, it includes a PI (XML processing instruction) at the top of the document that identifies the corresponding template solution so that the document is always connected with that specific form template. In the same way, you can open any XML of that namespace with that InfoPath form template.

For more information, see InfoPath 2003.

Microsoft Office Access 2003. Access uses custom XML schema primarily for importing and exporting data for greater ease of data exchange with other systems. You can also apply XSL transforms during an import or export, providing you with more flexibility over the shapes of XML that you can use.

When importing XML data, if the XML refers to an accompanying schema, Access recognizes data types based on the schema definition. However, importing XML data into Access does not require a schema. If there is no schema reference, Access infers a structure from the incoming data.

Access also offers more flexibility than previous versions of Access for exporting data as XML. You can limit an export to only data selected with respect to current Filter and Sort views. Access can also export related tables as XML. This way, you can include hierarchical data in one standard XML file for consumption in other systems.

Figure 3. Import XML options UI in Access 2003

All support for importing and exporting XML is available through UI objects as well as programmatically. Figure 3 shows the available dialog to import XML. To enable this, there are enhancements to the XML object model, including a new TransformXML method and additional parameters for the ExportXML method.

Suggested Next Steps

Learn more about the XML schema standard: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnxml/html/understandxsd.asp


Follow a basic walk-through using custom XML with Word: http://msdn.microsoft.com/office/understanding/word/articles/default.aspx?pull=/library/en-us/odc_wd2003_ta/html/odc_wd11xml.asp

Read a technical article on the new Word XML features: http://msdn.microsoft.com/office/understanding/xmloffice/gettingstarted/default.aspx?pull=/library/en-us/odc_wd2003_ta/html/odc_wdnew2k3xmlom.asp

Download the Word XML Toolbox to help with Word XML development: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnofftalk/html/odc_office01012004.asp


© 2006 Microsoft Corporation. All rights reserved. Page 11 By using or providing feedback on these materials, you agree to the attached license agreement.

To comment on this paper or request more documentation on these developer features, contact us at O12Devdx@microsoft.com. We look forward to hearing from you.

Document info
Document views271
Page views272
Page last viewedFri Jan 20 21:00:44 UTC 2017