Description
The class ID of the RDS.DataControl object is BD96C556-65A3-11D0-983A-00c04FC29E33.
For basic applications, only the SQL, Connect, and Server properties of the RDS.DataControl object are required to automatically call the default business object RDSServer.DataFactory.
All properties in RDS.DataControl are optional because custom business objects can replace their features.
Use a RDS.DataControl object to link a single query result to one or more visual controls. For example, suppose you write code requested by the customer data query, such as name, residence, birth, age, and priority customer status, you can display your customer name, age and residence in three text boxes using a single RDS.DataControl object. District, and display "Priority Customer Status" in the check box, and all data is displayed in the grid control.
Use different RDS.DataControl objects to link multiple query results to different visual controls. For example, suppose you use a query to obtain customer information, and use the second query to obtain information from the customer's purchase. If you want to display the result of the first query in three text boxes and a check box, display the result of the second query in the grid control, you must do the following when using the default business object (RDSServer.DataFactory) :
Add two RDS.DATACONTROL objects to the web page. Two queries are written for each SQL attribute of the two RDS.DataControl objects. A RDS.DataControl object contains SQL queries that request customer information, and the other includes queries that requested customers to buy a product list. In the Object tag of each binding control, specify the DATAFLD value so that the data value to be displayed in each visual control will be set.
There is no limit to the RDS.DataControl object that can be embedded in a single web page via the Object tag.
When defining a RDS.DataControl object on a web page, you can use non-zero HEIGHT and WIDTH values, such as 1 (to avoid including excess space).
The remote data service client component is already part of the Internet Explorer 4.0 installer, so the RDS.DataControl object tag does not have to contain the CodeBase parameter.
Test control
The following table lists the data identification controls that use with the RDS.DataControl objects and associated clients and have passed the test. Other controls can also be used with remote data services, but have not been tested.
Control Name File Name Class ID (CLSID) SSDBGRIDSDATB32.OCX (SHERIDAN) AC05DC80-7DF1-11D0-839E-00A024A94B3A Using Internet Explorer 4.0, these two can only be used when the HTML control and ActiveX® control are marked as a room model control The control is bound to the data.
The above controls are not published via remote data service, but can be used as part of Microsoft® Visual Basic®, Enterprise Edition or from Sheridan Systems, Inc..
IMPORTANT The ActiveX controls that cannot be redistributed in any way are deployed for remote data service examples. They are provided as an example of an example application, and they are not restricted to others without any circumstances.
Microsoft Visual Basic User RDS.DataControl is only for web-based applications. The Visual Basic client application does not require it.
DataFactory object (RDSServer)
The default server-side business object implements a way to read / write data access to the specified data source of the client application.
Description
The RDSServer.DataFactory object is designed to receive server-side automation objects that receive client requests. During the implementation of the Internet, the object resides in the web server and instantiated by the ADISAPI component. The RDSServer.DataFactory object provides read and write access to the specified data source, but does not contain any validity or business rule logic.
If the method used is valid in the RDSServer.DataFactory and RDS.DataControl objects, the remote data service uses the RDS.DataControl version in the default state. Basic programming applications are used by default, and RDSServer.DataFactory is used as a regular server-side business object in this scenario.
If you want the web application to handle the server-side process for specific tasks, you can replace RDSServer.DataFactory with custom business objects.
You can create a server-side business object that calls the RDSServer.DataFactory method, such as query and createrecordset. This will help to add functions to business objects using existing remote data service technology.
The class ID of the RDSServer.DataFactory object is 9381d8f5-0288-11d0-9501-00aa00b911a5.
