What's the diff. between DataSet and DataTable and other Basic Q's

23 Mar 2006 9:37 AM

Burning_Ranger

I have a database with several tables all linked together using
relationships, I am trying to build a system in VB .NET utilising this
database.

I have some Q's:
1. I've followed some ADO.NET tutorials and they all use databases with
1 table. The tutorials use a DataTable to hold a copy of the table in
memory, but I get the impression now that DataSet's are the thing to
use. How does a DataSet differ from a DataTable?

2. My Database has referential integrity set, will ADO.NET recognise
that the tables have relationships and update data automatically that
is linked by referential integrity or do I have to specify the
relationships again in VB.

3. If I'm using a DataTable and use the following code to reference a
particular field of a particular record, what's the equivalent if I'm
using a DataTable?

txtCompany.Text =
dtCustomer.Rows(intRowPos)("CustomerCompany").ToString

4. The books I have tend to all use wizards to make the ADO.NET
connection and tend to use bound controls. I've read that this is not a
good way to use ADO.NET, isn't it?

If someone could point me to a good tutorial that shows how to build
basic app utilising a database, DataSets etc or something similar
(without wizards or bound controls), that would be appreciated. Thanks.

23 Mar 2006 2:50 PM

Marina Levit [MVP]

1. A dataset is a collection of one or more datatables. A datatable is what
actually contains data
2. I believe you would have to specify those relationships yourself
3. Huh?
4. It is not a good way to write real applications. I recommend you code it
yourself

I think if you do a google search you will find a ton of good examples,
tutorials, faqs, etc.

Show quote

"Burning_Ranger" <aziz***@googlemail.com> wrote in message
news:1143106652.976112.13850@t31g2000cwb.googlegroups.com...
>I have a database with several tables all linked together using
> relationships, I am trying to build a system in VB .NET utilising this
> database.
>
> I have some Q's:
> 1. I've followed some ADO.NET tutorials and they all use databases with
> 1 table. The tutorials use a DataTable to hold a copy of the table in
> memory, but I get the impression now that DataSet's are the thing to
> use. How does a DataSet differ from a DataTable?
>
> 2. My Database has referential integrity set, will ADO.NET recognise
> that the tables have relationships and update data automatically that
> is linked by referential integrity or do I have to specify the
> relationships again in VB.
>
> 3. If I'm using a DataTable and use the following code to reference a
> particular field of a particular record, what's the equivalent if I'm
> using a DataTable?
>
> txtCompany.Text =
> dtCustomer.Rows(intRowPos)("CustomerCompany").ToString
>
> 4. The books I have tend to all use wizards to make the ADO.NET
> connection and tend to use bound controls. I've read that this is not a
> good way to use ADO.NET, isn't it?
>
>
> If someone could point me to a good tutorial that shows how to build
> basic app utilising a database, DataSets etc or something similar
> (without wizards or bound controls), that would be appreciated. Thanks.
>