InfoPath 2003 Solution Center

XML Data

How to handle mixed content elements in XML documents in InfoPath 2007 and in InfoPath 2003
Describes how InfoPath handles a schema that has mixed content for a form data source. First, you createa a schema for mixed content. Then you create an InfoPath form that uses the schema for a data source.
How to use script for cascading deletes in tables that have a master/detail relationship in InfoPath
Provides code sample and instructions to delete detail items that are linked by key field to a master item that is deleted.
How to submit an InfoPath form to a Windows SharePoint Services document library
Describes how to design a form template that uses script to submit form data to a Windows SharePoint Services (WSS) document library. This article also discusses how to submit form data to a WSS document library by using the UI in InfoPath 2003 SP1.

You cannot create a form from a Web service that returns an ADO.NET dataset in InfoPath 2003
Describes a limitation in Office InfoPath 2003. InfoPath cannot use the XML data that is returned by an ADO.NET dataset. This article includes a workaround that uses Visual Basic .NET.
XML files may open in Internet Explorer instead of opening in the expected Office program when the ContentType header contains the charset parameter
Discusses a problem that occurs when the ContentType header contains the charset parameter. Your XML file may open in Internet Explorer instead of opening in the expected Office program.
Expression box may return incorrect results for mathematical expressions in InfoPath 2003 or in InfoPath 2007
Discusses the incorrect results that you may receive when you add an expression box. This occurs when you add an expression box that evaluates a mathematical expression that involves decimal numbers. Includes the steps to reproduce the problem.
You cannot create a form from a Web service that returns an ADO.NET dataset in InfoPath 2003
Describes a limitation with Office InfoPath. InfoPath cannot use the XML data that is returned by an ADO.NET dataset. You can work around this problem by using Visual C# .NET. Two workarounds are described.