Microsoft KB Archive/190411

= How To Bind a DataReport To an ADO Recordset at Run Time =

Article ID: 190411

Article Last Modified on 3/2/2005

-

APPLIES TO


 * Microsoft Visual Basic 6.0 Professional Edition
 * Microsoft Visual Basic 6.0 Enterprise Edition
 * Microsoft Data Access Components 2.5
 * Microsoft Data Access Components 2.6
 * Microsoft Data Access Components 2.7

-



This article was previously published under Q190411



SUMMARY
The DataReport is a powerful tool and it's easy to build complex reports by dragging and dropping fields out of the DataEnvironment window. However, there are times when you may want to bind the DataReport directly to an ActiveX Data Objects (ADO) recordset rather than to the DataEnvironment. For example, you may have built a hierarchical query with ADO, or you may have an n-tier application that receives a recordset from a business object.

This article helps you understand how to bind a DataReport directly to an ADO recordset.



MORE INFORMATION
First, build a hierarchical query with the DataEnvironment. Next, create a simple DataReport that is based on your query and bound to the DataEnvironment.

Use the DataEnvironment to connect to the Northwind database (NWind.mdb) that is included with Visual Basic by following these steps:  Create a new Standard EXE project in Visual Basic. Add a DataEnvironment to that project and rename it deCustomerOrders. Rename the initial connection to cnNWind. Set the connection to use the Microsoft.Jet.OLEDB.4.0 OLE DB provider. Locate the Northwind database on your machine. Add a command to the connection and rename it Customers. Set the Customers command to query the Customers table.</li> Add a child command to the Customers command and rename it Orders.</li> Set the Orders command to query the Orders table.</li> Relate the two commands on the CustomerID field on the Relation tab.</li> Add a DataReport to the project and rename it rptCustomerOrders.</li> Set the DataSource property of the DataReport to deCustomerOrders.</li> Set the DataMember property of the DataReport to Customers.</li> Right-click on the DataReport and clear "Show Report Header/Footer".</li> Right-click on the DataReport and clear "Show Page Header/Footer".</li> Right-click on the DataReport and select "Insert Group Header/Footer".</li> Drag the CustomerID and CompanyName fields from the Customers command in the DataEnvironment onto the Group Header section.</li> Drag the OrderID and OrderDate fields from the Orders command in the DataEnvironment onto the Detail section.</li> Add a CommandButton to your form.</li>  Add the following code to your form: Private Sub Command1_Click rptCustomerOrders.Show End Sub </li> Run the project, click on the CommandButton and you should see the report with the customer and order information.</li>  To bind the DataReport directly to the hierarchical recordset generated by the DataEnvironment, add the following code: Private Sub Form_Load Dim intCtrl As Integer With rptCustomerOrders Set .DataSource = Nothing .DataMember = "" Set .DataSource = deCustomerOrders.rsCustomers With .Sections("Section2").Controls For intCtrl = 1 To .Count If TypeOf .Item(intCtrl) Is RptTextBox Or _ TypeOf .Item(intCtrl) Is RptFunction Then .Item(intCtrl).DataMember = "" End If              Next intCtrl End With .Show End With End Sub </li></ol>

NOTE: If you omit steps 13 and 14, you need to change "Section2" to "Section6" in the preceding code.

RESULT: Run the project, and you should see the report with the customer and order information.

The DataReport uses the DataSource and DataMember properties to find the top-level command on which the report is based. For example, if you have a hierarchical query in the DataEnvironment containing Customers, Orders, and Order Details information but you only want to show the Orders and Order Details information, then you should set the DataSource property to be the DataEnvironment, and the DataMember property to be the Orders command.

Each field on the DataReport has two properties that allow the DataEnvironment to determine what information to show on the report:
 * DataMember
 * DataField.

Use the DataMember property to select the level of the hierarchy that contains the information you want to display. Use the DataField property to select the field you want to display.

For example, the CustomerID field is in both the Customers and the Orders table. If you want to show the CustomerID field with the rest of the customer information, set DataMember to Customers. If you want to show the CustomerID with the rest of the Order information, set DataMember to Orders.

When you bind directly to a recordset object as shown in step 21, the DataSource property of the DataReport should be set to the recordset object and the DataMember property should be set to an empty string. For the fields on the report, the DataMember property of the top-level recordset information (customer information in this case) should be set to an empty string. For information other than that which is in the top-level recordset (Order information in this case), the DataMember property of the report TextBoxes should be set to the name of the command (Orders in this case).

Additional query words: DataReport runtime

Keywords: kbhowto kbdatabinding kbcode KB190411

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.