Microsoft Office Tutorials and References
In Depth Information
Understanding the Microsoft Office InfoPath object model
Let's suppose your company uses Microsoft SharePoint to manage the process of
expense reporting; the developers in your IT department might design an InfoPath
expense form that enables users to submit data directly to SharePoint, which in
turn routes that data to the appropriate department for approval. One of the main
advantages of Microsoft InfoPath 2007 is that you can use it to quickly create a
frontend for your input form.
Understanding the Microsoft Office InfoPath
If you're eager to leverage Microsoft Office InfoPath functionality in enterprise
software applications, you may be pleased to discover that the VSTO InfoPath object
model provides most of the functionality of Microsoft Office InfoPath. The Microsoft
Office InfoPath 2007 object model provides improved support for managed code
when compared to the previous version of the VSTO InfoPath object model.
The Microsoft Office InfoPath object model is a Component Object Model COM ). (
The importance of COM is that it is a language-neutral way of implementing objects
that can be used in different environments. The InfoPath object model can be used
to interact with InfoPath forms and their underlying XML documents. It is similar
to other Microsoft Office application object models—the object model implements
interfaces for collections, objects, properties, methods, and events.
The InfoPath 2007 object model is not supported in Microsoft Office
InfoPath 2003. So, if you use the InfoPath 2007 object model to write
code for your Microsoft Office InfoPath 2007 solution, and then decide
to make that form template compatible with Microsoft Office InfoPath
2003, you must remove the code or rewrite it using the InfoPath 2003
When Microsoft launched InfoPath 2007, they added several new objects, collections,
and enumerations to the existing object model.
Previously, in the InfoPath 2003 object model, objects were packed in three
namespaces: Microsoft.Office.InfoPath , Microsoft.Office.Interop.
InfoPath , and Microsoft.Office.Interop.InfoPath.Xml . In the new version,
all objects and collections related to InfoPath are packed in the single namespace
The following table provides a quick overview of the InfoPath object model. It shows
the frequently-used objects whose names were changed depending on their usage