It is a wrong answer. Data set store multiple table from database while recordset only one table at time.Dataset store date as xml formate

As far as i have studies i know that ADO(Active Data Objects) has several problems associated like unwieldness of disconnected record set. So ado.net overcome this problem and gives best support fro disconnected environment useing dataset

Hi All



Ans:

a. DataSet is Disconnected architecture while ADO Recordset is Connected.
b. Dataset catch bluk Data where recordSet retrive one record one at time

1) A DataSet can represent an entire relational database in memory complete with tables relations and views A Recordset can not.

2) A DataSet is designed to work without any continuing connection to the original data source; Recordset maintains the contentious connection with the original data source.

3) There's no concept of cursor types in a DataSet They are bulk loaded while Recordset work with cursors and they are loaded on demand.

4) DataSets have no current record pointer you can use For Each loops to move through the data. Recordsets have pointers to move through them.

1. ASP.NET DataSet is Designed for connected access.

2. Dataset is a data structure which represents the complete table data at same
time.

3. Dataset is just a data store and manipulation is done through DataAdapters in
.NET.

4. DataSet can contain multiple tables

Retrieving data from more than one table or source does not require a JOIN.

5. XML like HTML is plaintext: Firewall friendly

About RecordSet:

1. ADO RecordSet is disconnected Architecture.

2. Recordset provides data one row at a time.

3. Recordset has the logic to update and manipulate data

4. The RecordSet is the central data container

RecordSet is one (1) table that contains all the data

Retrieving data from more than one table or source requires a database JOIN.

5. Problems marshalling through firewalls (DCOM binary)