I've used datatables and datasets before.  Datasets being able to hold
more than one table and datatables being only one table.  My mind keeps
coming up with recordsets.  I can't remember how they fit into the picture.

I'm going to be reading some records from a table in a sql db.

cj,

A recordset is ADO classic terminology.

In ADO.Net you need to be able to work with dataadapters, datasets,
datatables, datarows, etc. But not recordsets.

Kerry Moorman


Show quoteHide quote

Thanks, I suspected my mind might be regressing.


Kerry Moorman wrote:
Show quoteHide quote

In .NET a Dataset is a container for one or more DataTables. They are
completely database unaware and agnostic.... think of it as an Array of
Arrays of Arrays. IMHO, it doesn't even belong in the System.Data namespace,
but should be in System.Collections.

A DataAdapter communicates with a database and fills the Dataset's tables.
It's the "bridge."

In .NET 2.0, the highly RETARDED throwback to the "1990's ADO" new
"TableAdapter" is an easier to use wrapper around the DataAdapter. It is
tightly coupled to a Dataset (violating all sorts of true n-tier principles)
and is for the braindead folks who couldn't grasp the way the original
DataAdapter worked.

Show quoteHide quote

Can't modify instance of a class from within the class!
WebBrowser Control Printing
Garbage collection, Unmanaged code and SafeArrays
creating independant application vb 2005 express edition
Fastest way to load jpg images ?
Regular Expression Question
Single event handler for menu
Access digital camera
How to.... Question.....
Enum and FlagsAttribute