I have a book called "Hitchhiker's Guide to Visual Studio and SQL
Server".  It has a chapter on using dataAdapters, and another chapter
on using tableAdapters.  The problem is, they seem to overlap in what
they can do, and I don't know when I would use one and when I would
use the other?  Furthermore VB 2003 seemed to use one, and VB 2005
seems to use the other mostly (at least when you drag and drop).
If I just want to learn the latest method of using VB-2005 with
databases, should I learn both adapters?  Or just the Table Adapter?
And how would I know, in a given application, which one to choose?
Thanks,
HA

A TableAdapter is a visual component that VS uses to "show" you the details
of your connection and dataadapter.  You wouldn't, for example, make an
instance of one of these in code and use it that way.  A DataAdapter is
still the actual object that bridges the gap between the connected and
disconnected ADO .NET objects and, if you were writing code to perform your
data access, you'd use this.


<HONOREDANCES***@yahoo.com> wrote in message
Show quoteHide quote

Hi,

In version 2003 we had the DataAdapter and the Dataset. A part of the
dataset is the DataTable. For some who were used to the recordset that was
to difficult.

Then we got the TableAdapter as stand alone part in version 2005, because
that would be the solution, however probably not as wanted because now for
2008 we have Linq.

(Spoken this means in Dutch "tricky or dangerous").

I don't know why that name is choosen, however I am not yet able to give a
realistic opinion about Linq to be able to presume what there will be in
2011.

I know from a message the ideas of the writer of the Hitchhiker about this,
he will probably use other/more words to answer (By instance because he can
start earlier in past). However his intention will probably not be much
different.

Cor

Getting a subset of DataRows from a DataTable
vs2008 or not
Linq2Sql issues
DataTable foreign key
prompt user to select from recordset.