RDSIE3.DataControl Object

The RDSIE3.DataControl object binds a data query Recordset to one or more controls (for example, a text box, grid control, or combo box) to display the ADOR.Recordset data on a Web page.

Syntax

<OBJECT CLASSID="clsid:9381D8F2-0288-11D0-9501-00AA00B911A5" ID="RDSIE3.DataControl"

CODEBASE="HTTP://MyServer/MSADC/msadc11.cab#version=1,1,0000,0">

<PARAM NAME="Bindings" VALUE="ControlNames;">

<PARAM NAME="Connect" VALUE="DSN=DSNName; UID=usr;PWD=pw;">

<PARAM NAME="Server" VALUE="http://awebsrvr">

<PARAM NAME="SQL" VALUE="QueryText">

</OBJECT>

Methods

CancelUpdate, MoveFirst, MoveLast, MoveNext, MovePrevious, Refresh, SubmitChanges

Properties

Bindings, Connect, Recordset, Server, SQL

Remarks

Remote Data Service provides the msadc11.cab file to simplify the deployment of Remote Data Service-enabled Web pages. By using this file, you can take advantage of HTML's automatic code download feature. You can use the automatic code download by specifying the .cab file path and name in a CODEBASE parameter when you define an RDSIE3.DataControl object. When the msadc11.cab file is downloaded, it automatically installs the required client files. The following code shows how to use the HTML CODEBASE parameter in the OBJECT tags of the RDSIE3.DataControl object:

<OBJECT CLASSID="clsid:9381D8F2-0288-11d0-9501-00AA00B911A5"
	ID="ADC1"
	CODEBASE="HTTP://MyServer/MSADC/msadc11.cab"  
	WIDTH=1 HEIGHT=1>
	<PARAM NAME="BINDINGS" VALUE="Grid1;">
</OBJECT>

Note When you use the CODEBASE parameter in your RDSIE3.DataControl OBJECT tag, you can use the optional #Version syntax to indicate which version to download. The Build number must always be four character, therefore, you might need to pad the build number with zeros. For example, the number 0127 in the following syntax is the number of the most recent build to download (in this case, version 1.1, Build 127):

CODEBASE="HTTP://<WebSvrName>/MSADC/msadc11.cab#Version=1,1,0127,0"

If you want your page to always redownload the file, use -1 values for all of the #Version values (for example, msadc11.cab#Version=-1,-1,-1,-1; note that you donÆt need to pad the Build number in this case). Also, if the build number is set to a version higher than is actually available, the page will download the version in the path each time. Neither of these options is recommended because they result in frequent downloads and path checking.

The RDSIE3.DataControl object has two class IDs:

A class ID that you should use for Web pages that use all single-threaded ActiveX controls: 9381D8F2-0288-11D0-9501-00AA00B911A5. This is the default class ID.
A class ID that you should use for Web pages that use apartment model ActiveX controls (which will be available in the near future): C5C18AE2-4D6E-11D0-9823-00C04FC29E30.
Use one RDSIE3.DataControl object to link the results of a single query to one or more visual controls. For example, suppose you code a query that requests customer data such as Name, Residence, Place of Birth, Age, and Priority Customer Status. You can use a single RDSIE3.DataControl object to display a customer's Name, Age, and Region in three separate text boxes, Priority Customer Status in a check box, and all the data in a grid control:
```
<OBJECT CLASSID="clsid:9381D8F2-0288-11d0-9501-00AA00B911A5"
 ID="ADC1">
	<PARAM NAME="Bindings" VALUE="SText1.Text=Name; SText2.Text=Age; SText3.Text=State; SCheck1.Text=Status; Sgrid">
	<PARAM NAME="SQL" VALUE="Select * from CustomerData">
	<PARAM NAME="Connect" VALUE=" DSN=SalesDB; UID=SMgr;PWD=;">
	<PARAM NAME="Server" VALUE="http://SalesWeb">
</OBJECT>
```
Use different RDSIE3.DataControl objects to link the results of multiple queries to different visual controls. For example, suppose you use one query to obtain information about a customer, and a second query to obtain information about merchandise the customer has purchased. You want to display the results of the first query in three text boxes and one check box, and the results of the second query in a grid control. If you use the default business object (RDSServer.DataFactory object), you need to do the following:
- Code two RDSIE3.DataControl objects.
- Write two queries, one for each SQL property of the two RDSIE3.DataControl objects. One RDSIE3.DataControl object will contain a SQL query requesting customer information, the second will contain a query requesting a list of merchandise the customer has purchased.
- In each RDSIE3.DataControl object's Bindings property, set the values for the data you want to display in each visual control.
There is no count restriction on the number of RDSIE3.DataControl objects that you can embed via OBJECT tags on a single Web page.

For a basic scenario, you only need to set the Bindings, SQL, Connect, and Server properties of the RDSIE3.DataControl object, which will automatically call the default business object, RDSServer.DataFactory.

All the properties in the RDSIE3.DataControl are optional because custom business objects can replace their functionality.

When you define the RDSIE3.DataControl object on a Web page, use non-zero Height and Width values such as 1 (to avoid the inclusion of extra space).

Example