Hi!

I got the impression that you can add/edit data with both datatable and 
dataview.

What's the differences between these two, and when should they be used.

thanks

- Frode.

Frode,
Think of a DataView as one way through which you can view, organize, or
arrange data in a DataTable. While it is possible to add/edit data within a
DataView, this object is quite limited compared to the DataTable.
Terrence  

-----Original Message-----
From: Frode [mailto:fstroemm@o...] 
Sent: Wednesday, March 27, 2002 7:17 AM
To: ADO.NET
Subject: [ado_dotnet] DataTable vs DataView

Hi!

I got the impression that you can add/edit data with both datatable and 
dataview.

What's the differences between these two, and when should they be used.

thanks

- Frode.

Frode the difference is that the dataview is designed to work with SQL
queries and the table view is not.  I would argue that the data view is far
more flexible and powerful than the directly viewing the table information
through tableview unless your intent is to modify the table structure.

Think of datasets as detached recordsets.  The the dataviews are collections
of pointers into the dataset's data.  Because of this, the data stays put,
yet the dataview can still filter and sort the data for you.  For example,
you might provide a filter so restrictive that only a record or 2 (maybe
none even) pass through.  When you are done, you do not need to reload your
data from the database server again -- you just change the filter
expression!  You still update the data kept in the dataset when you reassign
the data you can "see" in the dataview.  Because the dataset is
disconnected, you need to use the update method on the dataset when you are
done to store your changes in the database. This is really powerful, and
worth the extra effort to learn how to use it.


----- Original Message -----
From: "Frode" <fstroemm@o...>
To: "ADO.NET" <ado_dotnet@p...>
Sent: Tuesday, March 26, 2002 7:17 PM
Subject: [ado_dotnet] DataTable vs DataView


> Hi!
>
> I got the impression that you can add/edit data with both datatable and
> dataview.
>
> What's the differences between these two, and when should they be used.
>
> thanks
>
> - Frode.

A dataset can include more than one table, including the relationships between the tables, what you mean
is a datatable.

- Kruse

-----Original Message-----
From: Richard Ainsley <rainsley@p...>
To: ADO.NET <ado_dotnet@p...>
Sent: Wed Mar 27 01:22:30 2002
Subject: [ado_dotnet] Re: DataTable vs DataView

Frode the difference is that the dataview is designed to work with SQL
queries and the table view is not.  I would argue that the data view is far
more flexible and powerful than the directly viewing the table information
through tableview unless your intent is to modify the table structure.

Think of datasets as detached recordsets.  The the dataviews are collections
of pointers into the dataset's data.  Because of this, the data stays put,
yet the dataview can still filter and sort the data for you.  For example,
you might provide a filter so restrictive that only a record or 2 (maybe
none even) pass through.  When you are done, you do not need to reload your
data from the database server again -- you just change the filter
expression!  You still update the data kept in the dataset when you reassign
the data you can "see" in the dataview.  Because the dataset is
disconnected, you need to use the update method on the dataset when you are
done to store your changes in the database. This is really powerful, and
worth the extra effort to learn how to use it.


----- Original Message -----
From: "Frode" <fstroemm@o...>
To: "ADO.NET" <ado_dotnet@p...>
Sent: Tuesday, March 26, 2002 7:17 PM
Subject: [ado_dotnet] DataTable vs DataView


> Hi!
>
> I got the impression that you can add/edit data with both datatable and
> dataview.
>
> What's the differences between these two, and when should they be used.
>
> thanks
>
> - Frode.



This message is for the named person's use only. It may contain sensitive and private proprietary or legally privileged information.
No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient, please immediately
delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or
indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. CREDIT SUISSE
GROUP and each legal entity in the CREDIT SUISSE FIRST BOSTON or CREDIT SUISSE ASSET MANAGEMENT business units of CREDIT SUISSE
FIRST BOSTON reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are
those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views
of any such entity.
Unless otherwise stated, any pricing information given in this message is indicative  only, is subject to change and does not
constitute an offer to deal at any price quoted. Any reference to the terms of executed transactions should be treated as 
preliminary only and subject to our formal written confirmation.