you have created a data connection, you can create subforms and
fields corresponding to all or some of the data. Often there is
excess data that you do not need; therefore, selectively creating
subforms and fields may be preferable to auto-creating them all.
Another approach is to design the form design first and then use
the Data View palette to bind specific fields in the form design
to specific data nodes in the hierarchy.
Designer determines which field to create when you bind specific
fields from an XML schema, XML file, or WSDL file, or when you generate
fields from the Data View palette, based on the types of elements
and attributes. For example, an image will be mapped to the Static
Image object in the form design.
When you drag a node from the Data View palette onto the page
to create a field or subform, the name of an XML schema element
or attribute is used as the name of the generated field or subform.
The element or attribute name is also used as the initial caption
for the field. The binding value for the field is used to bind the field
to the data node described by the element or attribute declaration
in the schema.
The following See also section lists topics that provide more
information about how Designer determines which field to create
when you bind fields from an XML schema, XML file, or WSDL file.