| Microsoft XML Core Services (MSXML) 5.0 for Microsoft Office - XML Developer's Guide |  |
Using the XML Data Source Object
You can either use the <OBJECT> element to refer to the XML data source object, or you can use data islands and the <XML> element.
The XML data source Microsoft® ActiveX® object can be inserted into an HTML page as follows.
<OBJECT width=0 height=0
classid="clsid:550dda30-0541-11d2-9ca9-0060b0ec3d39"
id="xmldso">
</OBJECT>
This can be used as an XML data provider in conjunction with the data binding features of Microsoft Internet Explorer 5.0 for binding XML data to HTML elements on the page.
To load XML into the data source object, use the Dynamic HTML (DHTML) XMLDocument property to get a Document Object Model (DOM), and then call the load method as follows:
<SCRIPT for=window event=onload>
var doc = xmldso.XMLDocument;
doc.load("books.xml");
if (doc.documentNode == null)
{
HandleError(doc);
}
</SCRIPT>
Inline XML
You can also provide the XML inline inside the <OBJECT> element, as shown in the following example.
<OBJECT width=0 height=0
classid="clsid:550dda30-0541-11d2-9ca9-0060b0ec3d39"
id="xmldso">
<favorites>
<favorite>
<name>Microsoft</name>
<url>http://www.microsoft.com</url>
</favorite>
</favorites>
</OBJECT>
You use script to load the data source object, as follows:
<SCRIPT for=window event=onload>
var doc = xmldso.XMLDocument;
doc.loadXML(xmldso.altHtml);
if (doc.documentNode == null)
{
HandleError(doc);
}
</SCRIPT>
Events Used with the XML Data Source Object
The XML data source object triggers events when the underlying XML data changes. These events are common among the XML data source object and the other supplied data source objects. For more information about events and the data source object, see "DHTML Event Model Support for Data Binding", in the DHTML documentation.
Viewing and Navigating a Subset of the Data
If you want a table to display a small portion of your XML data set, use the DATAPAGESIZE attribute on your <TABLE> element. The DATAPAGESIZE attribute indicates how many records to display in the table.
To navigate the table, you can use the nextPage, previousPage, firstPage, and lastPage methods to display different pages of the data.
Usually, you can provide buttons to view different pages of the data set with nextPage, previousPage, firstPage, and lastPage. For example, a button to view the next page can be written as follows.
<INPUT TYPE="button" VALUE="Next" ONCLICK="tbl.nextPage();">
To specify the table, you can use the following code.
<TABLE DATAPAGESIZE=1 ID=tbl DATASRC=#xmlData> ...Table... </TABLE>
This example sets the table to display one record (DATAPAGESIZE=1), identifies itself as tbl (ID=tbl), and uses a data source called xmlData.
To indicate which table the button refers to, use the ID attribute used with the <TABLE> element.
The ONCLICK attribute can also specify "previousPage", "firstPage", or "lastPage". For example, to create a button to display the first page, use the following.
<INPUT TYPE="button" VALUE="First Page" ONCLICK="tbl.firstPage();">
The $Text Data Field
When you bind data using the XML data source object, an automatic field called $Text is created. It contains the items in that record, concatenated. The following example demonstrates the $Text data field.
<HTML><HEAD></HEAD><TITLE></TITLE> <BODY> <XML ID="xmlParts"> <?xml version="1.0" ?> <parts> <part> <partnumber>A1000</partnumber> <description>Flat washer</description> <quantity>1000</quantity> </part> <part> <partnumber>S2300</partnumber> <description>Machine screw</description> <quantity>1000</quantity> </part> <part> <partnumber>M2400</partnumber> <description>Nail</description> <quantity>500</quantity> </part> </parts> </XML> <table datasrc=#xmlParts> <tr> <td><div datafld="partnumber"></div></td> <td><div datafld="$Text"></div></td> </tr> </table> </BODY> </HTML>
In this example, the table will consist of a column of part numbers (where datafld is equal to "partnumber") and a column containing the part number, description, and quantity concatenated (where datafld is equal to "$Text"). For example, the first row of the partnumber column will contain "S2300", while the second row of the $Text column will contain "S2300 Machine screw 1000". The $Text column contains the part number.
Rules for Assigning XML Elements and Attributes to Columns and Rows
The XML data source object follows a procedure for assigning elements and attributes to columns and rows in databound applications. XML is modeled as a tree with one element containing the entire hierarchy. For example, an XML description of a book can contain <chapter> tags, <figure> tags, and <section> tags. A <book> element can contain the subelements of <chapter>, <figure>, and <section>. When the XML data source object assigns rows and columns, the subelements, not the top-level element, are converted.
The XML data source object uses this procedure for converting the subelements.
Each subelement and attribute corresponds to a column in some rowset in the hierarchy.
The name of the column is the same as the name of the subelement or attribute, unless the parent element has an attribute and a subelement with the same name, in which case a "!" is prepended to the subelement's column name.
Each column is either a simple column containing scalar values, usually strings, or a rowset column containing subrowsets.
Columns corresponding to attributes are always simple.
Columns corresponding to subelements are rowset columns if either the subelement has its own subelements and/or attributes, or the subelement's parent has more than one instance of the subelement as a child. Otherwise, the column is simple.
When there are multiple instances of a subelement (under different parents), its column is a rowset column if any of the instances imply a rowset column; its column is simple only if all instances imply a simple column.
All rowsets have an additional column named $Text.
A simpler conversion takes place if you have set the JavaDSOCompatible flag to true. The JavaDSOCompatible flag makes the Internet Explorer 5.0 XML data source object compatible with the Java data source object supplied with Internet Explorer 4.0. To set the JavaDSOCompatible flag, you can use the <XML> element as follows:
<xml id="xmldata" JavaDSOCompatible=true> ...XML data </xml>
Or, you can use the following with the <OBJECT> element (using the <XML> element is recommended).
<OBJECT width=0 height=0
classid="clsid:550dda30-0541-11d2-9ca9-0060b0ec3d39"
id="xmldso">
<PARAM NAME="JavaDSOCompatible" value="true">
</OBJECT>
The following method is used for creating rows and columns when JavaDSOCompatible is true.
Any element that contains another element is automatically a rowset.
Elements that contain only text are columns.
Values stored in attributes are ignored.
For more information about the Java XML data source object, see "XML Data Source", in the DHTML documentation.
Using DTDs
If you use a document type definition (DTD) with your XML, the XML data source object uses the following method for converting elements and attributes to rows and columns.
Each subelement and attribute named by the DTD corresponds to a column in some rowset in the hierarchy.
The name of the column is the same as the name of the subelement or attribute, unless the parent element has an attribute and a subelement with the same name, in which case a "!" is prepended to the subelement's column name.
Each column is either a simple column containing scalar values, usually strings, or a rowset column containing subrowsets.
Columns corresponding to attributes are always simple.
Columns corresponding to subelements are rowset columns if either the DTD allows the subelement to have its own subelements and/or attributes, or the DTD allows the subelement's parent to have more than one instance of the subelement as a child. Otherwise the column is simple.
All rowsets have an additional column named $Text.
Content corresponding to the content model "ANY" is not included in the rowset hierarchy.