Shulou(Shulou.com)06/02 Report--

How to use applications to transfer ADO recordsets, this article introduces the corresponding analysis and answers in detail, hoping to help more partners who want to solve this problem to find a more simple and easy way.

In ADO.NET, the connection is opened for only enough time to perform database operations, such as Select or Update. You can read rows into the dataset and then use them without maintaining a connection to the data source. In ADO, recordsets can provide disconnected access, but ADO recordsets are mainly designed for connected access.

There is a significant difference between disconnect handling in ADO and ADO.NET. In the ADO recordset, you communicate with the database by calling the OLE DB provider. In ADO.NET, however, you communicate with the database through a data adapter (OleDbDataAdapter, SqlDataAdapter, OdbcDataAdapter, or OracleDataAdapter object), which invokes the API provided by the OLE DB provider or the underlying data source. The main difference between ADO and ADO.NET is that in ADO.NET, data adapters allow you to control how changes made to the dataset are transferred to the database by implementing performance tuning, performing data validation checks, or adding any other additional processing.

A general introduction to the extended ADO.NET

Explain the upgraded ADO.NET Entity Framewo in detail

Get ADO.NET Entity Data Model data introduction

Analyze the data of ADO.Net performance test

The picture shows the introduction of ADO.NET operation.

Note that data adapters, data connections, data commands, and data readers are the components that make up the .NET Framework data provider. Microsoft and third-party vendors may provide other providers that can also be integrated into Visual Studio. For information about different .NET data providers, see .NET data providers.

Share data between applications

It is much easier to transfer ADO.NET datasets between applications than to transfer recordsets that are ADO disconnected. To transfer ADO recordset disconnected recordsets from one component to another, use COM marshaling. To transfer data in ADO.NET, use a dataset, which can transmit XML streams. Compared to COM marshaling, the transfer of XML files provides the following convenience:

Richer data types

COM marshaling provides a limited set of data types (those defined by the COM standard). Because the transfer of datasets in ADO.NET is based on XML format, there are no restrictions on data types. As a result, components that share datasets can use any rich set of data types that these components typically use.

Performance

Network resources are used to transmit large ADO recordsets or large ADO.NET data sets; as the amount of data increases, so does the pressure on the network. Both ADO and ADO.NET allow you to reduce the amount of data transferred to a limited extent. But ADO.NET also provides another performance advantage: ADO.NET does not require data type conversions. ADO that needs to be marshaled by COM to transfer recordsets between components needs to convert the ADO data type to the COM data type.

This is the answer to the question about how to use the application to transmit the ADO recordset. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.