Database access sucks!

**W.G. Ryan eMVP** · Jul 21 '05, 08:03 PM

Re: Database access sucks!

If anything I think your complaint applies to the DataGrid component - not
ADO.NET.

Actually, you can bind a grid to all sorts of stuff - inlcuding a strongly
typed collection. dataViews are actually based on DataTables not datasets.

There's nothign stopping you from subclassing the grid to get the
functionality that you want. "It should just be a property" I guess,
unless you want multiselect which would entail two properties - or one that
you would need to iterate through.

The DataRowView is necessary b/c it can show four different states of the
datarow - Default - Current, Original and Proposed which can be very handy
particularly in a disconnected scenario where you want to show users the
original value and the stuff they changed - or just want to show them the
changed rows.

DataTable.Selec t for instance will give you an array of the rows that are
found - which in turn can be used to bind to a grid. This may be helpful.
You can set the RowFilter of a DataView to whatever search conditions you
want so only those show.

I admit the dataGrid for Winforms leaves a little to be desired, but again
this has Nothing to do with ADO.NET. I think you'll find it's easy enough
to write a few of your own controls (or use Infragistics for instance) that
you can reuse and tailor to your particular needs.

HTH,

Bill

--
W.G. Ryan MVP (Windows Embedded)

TiBA Solutions
www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"Relaxin" <me@yourhouse.c om> wrote in message
news:eP8eDTW7EH A.4028@TK2MSFTN GP15.phx.gbl...[color=blue]
> It is just me or has MS created some of the worst ways to access and[/color]
display[color=blue]
> data?
>
> You can use a DataSet, but if you want to sort or filter the data to must
> use a DataView which is created from a DataSet.
>
> But, if you sort by using the Grid (clicking the header) you can no longer
> use the DataSet (or maybe the DataView, if that is what you are using) to
> locate the record that the user has selected!!
>
> You have to write code to get the current position...this should just be a
> property!!
>
> Also, can someone explain to me why does the FindRows return
> DataRowView...w hat can you do with a DataRowView, I haven't figure out a[/color]
way[color=blue]
> to load this data into a new DataView or a DataSet (if there is a way,
> please explain it to me). It seems that the FindRows should have just
> return a new DataView!!
>
> I understand why all of the necessary data access components are broken[/color]
out[color=blue]
> into many different parts, but why not ALSO build a component that
> encompasses all of the components and use that as an "enhanced DataSet"[/color]
that[color=blue]
> can also be used as a Datasource to the grid and other components.(Thi s is
> something that I have already done for myself.)
>
> Maybe it's because I'm coming from Borland and expect top notch[/color]
development[color=blue]
> tools/comopnents...wh ere there VCL Framework and Data Access components[/color]
were[color=blue]
> THE BEST!!!
>
> But I had to leave Borland because their management said that they were
> killing the Borland C++ Builder (BCB) product about 6 months ago. But,[/color]
they[color=blue]
> just recently announced that they had a change of heart and will now[/color]
support[color=blue]
> BCB.
> That's a little to flaky for me, so I jumped ship and moved to MS.
>
> But with what I have seen in VS.NET (C#), I might have to talk my chances
> with Borland.
>
>
>[/color]

**W.G. Ryan eMVP** · Jul 21 '05, 08:03 PM

Re: Database access sucks!

You may find this link helpful as well

http://weblogs.asp.net/codemouse/

--
W.G. Ryan MVP (Windows Embedded)

TiBA Solutions
www.tibasolutions.com | www.devbuzz.com | www.knowdotnet.com
"Relaxin" <me@yourhouse.c om> wrote in message
news:eP8eDTW7EH A.4028@TK2MSFTN GP15.phx.gbl...[color=blue]
> It is just me or has MS created some of the worst ways to access and[/color]
display[color=blue]
> data?
>
> You can use a DataSet, but if you want to sort or filter the data to must
> use a DataView which is created from a DataSet.
>
> But, if you sort by using the Grid (clicking the header) you can no longer
> use the DataSet (or maybe the DataView, if that is what you are using) to
> locate the record that the user has selected!!
>
> You have to write code to get the current position...this should just be a
> property!!
>
> Also, can someone explain to me why does the FindRows return
> DataRowView...w hat can you do with a DataRowView, I haven't figure out a[/color]
way[color=blue]
> to load this data into a new DataView or a DataSet (if there is a way,
> please explain it to me). It seems that the FindRows should have just
> return a new DataView!!
>
> I understand why all of the necessary data access components are broken[/color]
out[color=blue]
> into many different parts, but why not ALSO build a component that
> encompasses all of the components and use that as an "enhanced DataSet"[/color]
that[color=blue]
> can also be used as a Datasource to the grid and other components.(Thi s is
> something that I have already done for myself.)
>
> Maybe it's because I'm coming from Borland and expect top notch[/color]
development[color=blue]
> tools/comopnents...wh ere there VCL Framework and Data Access components[/color]
were[color=blue]
> THE BEST!!!
>
> But I had to leave Borland because their management said that they were
> killing the Borland C++ Builder (BCB) product about 6 months ago. But,[/color]
they[color=blue]
> just recently announced that they had a change of heart and will now[/color]
support[color=blue]
> BCB.
> That's a little to flaky for me, so I jumped ship and moved to MS.
>
> But with what I have seen in VS.NET (C#), I might have to talk my chances
> with Borland.
>
>
>[/color]

**Marc Scheuner [MVP ADSI]** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

>It is just me or has MS created some of the worst ways to access and display[color=blue]
>data?[/color]

It's just you! :-) Hey, you almost *ASKED* for that! ;-)

Seriously, ADO.NET might not be totally intuitive at first, but it
really rocks - it packs a LOT of power!
[color=blue]
>You can use a DataSet, but if you want to sort or filter the data to must
>use a DataView which is created from a DataSet.[/color]

You can use a DataView (based and created from a *DataTable* - not a
DataSet - watch your terms!! You gotta be EXACT to get things right!)
to sort and filter the data in any way, shape or form.

Heck, you can have your data stored in a DataTable, and look at it
through a dozen different data views - filtering and sorting to your
hearts' content! How powerful is that?
[color=blue]
>Also, can someone explain to me why does the FindRows return
>DataRowView... what can you do with a DataRowView, I haven't figure out a way
>to load this data into a new DataView or a DataSet[/color]

A DataRowView is just like a DataRow - only for a view. If you need
the underlying DataRow, just grab it from the .Row property of the
DataRowView - how easy is that?

I really think you ought to put a bit more brain power into learning
and understanding ADO.NET - you haven't grasped all the power behind
it just yet! Read a book, read the online help, study the samples -
it'll be worth it!

Marc
=============== =============== =============== =============== ====
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)i nova.ch

**Cor Ligthert** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

Marc,
[color=blue]
>
> It's just you! :-) Hey, you almost *ASKED* for that! ;-)
>[/color]
Why you wrote that. (I first did want you to give an answer and than answer
that again with). "It was only that I could not now".

:-)

Cor

**Relaxin** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

[color=blue]
>----- Original Message -----
>From: "Marc Scheuner [MVP ADSI]" <m.scheuner@ino va.SPAMBEGONE.c h>
>Newsgroups: microsoft.publi c.dotnet.genera l
>Sent: Tuesday, December 28, 2004 11:00 PM
>Subject: Re: Database access sucks![/color]
[color=blue]
> A DataRowView is just like a DataRow - only for a view. If you need
> the underlying DataRow, just grab it from the .Row property of the
> DataRowView - how easy is that?[/color]

That is exactly my point, why not just have FindRows return a DataView!!
[color=blue]
> I really think you ought to put a bit more brain power into learning
> and understanding ADO.NET - you haven't grasped all the power behind
> it just yet! Read a book, read the online help, study the samples -
> it'll be worth it!
>[/color]
I have and I've used the best. I also used and created components from
OLEDB.
ADO.NET has alot to be desired and they are also missing functionality that
OLEDB had.
Such as the different resultset types (Keyset, dynamic, forwardonly,
etc...).

With the .NET dataset, it forces you to load all of the data to the
client...this doesn't work so well when you database is mainly made up of
images!

I hate it when the vendor (MS) tells me how I should write my code by
removing functionality and not replacing it with something similar.

----- Original Message -----
From: "Marc Scheuner [MVP ADSI]" <m.scheuner@ino va.SPAMBEGONE.c h>
Newsgroups: microsoft.publi c.dotnet.genera l
Sent: Tuesday, December 28, 2004 11:00 PM
Subject: Re: Database access sucks!

[color=blue][color=green]
> >It is just me or has MS created some of the worst ways to access and
> >display
>>data?[/color]
>
> It's just you! :-) Hey, you almost *ASKED* for that! ;-)
>
> Seriously, ADO.NET might not be totally intuitive at first, but it
> really rocks - it packs a LOT of power!
>[color=green]
>>You can use a DataSet, but if you want to sort or filter the data to must
>>use a DataView which is created from a DataSet.[/color]
>
> You can use a DataView (based and created from a *DataTable* - not a
> DataSet - watch your terms!! You gotta be EXACT to get things right!)
> to sort and filter the data in any way, shape or form.
>
> Heck, you can have your data stored in a DataTable, and look at it
> through a dozen different data views - filtering and sorting to your
> hearts' content! How powerful is that?
>[color=green]
>>Also, can someone explain to me why does the FindRows return
>>DataRowView.. .what can you do with a DataRowView, I haven't figure out a
>>way
>>to load this data into a new DataView or a DataSet[/color]
>
> A DataRowView is just like a DataRow - only for a view. If you need
> the underlying DataRow, just grab it from the .Row property of the
> DataRowView - how easy is that?
>
> I really think you ought to put a bit more brain power into learning
> and understanding ADO.NET - you haven't grasped all the power behind
> it just yet! Read a book, read the online help, study the samples -
> it'll be worth it!
>
> Marc
> =============== =============== =============== =============== ====
> Marc Scheuner May The Source Be With You!
> Bern, Switzerland m.scheuner(at)i nova.ch[/color]

**Cor Ligthert** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

Relaxin,

Probably is your major mistake although you are not writing it, that you
compare a dataset with a recordset, what is not the case. A recordset is
comparable with a datatable.

The datatable has a lot of extra's above the recordset by instance a
dataview, with can show you data in a lot of ways. This newsgroup is not the
part to show all advantages from a datatable above a recordset.

And not to tell that there are only advantages in some cases can the
standard optimistic concurrency in my opinion be a disadvantage, however
modern disconnected use makes pessimistic concurrency in my opinion very
hard to do and should only be done when it is really needed

To select one or more datarows from a datatable you can use the
datatable.selec t
You can as well find a row in the datarow collection in a datatable by using
a datarowcollecti on.find
Or get a selection by using the dataview.rowfil ter
Or get a position of a datarow in a dataview by the dataview.find

You can use as well of course to narrow your datatable the different select
where clauses.

Maybe you can say it was more simple with the recordset because it had not
all those possibilities. The same as people who went from the T Ford to a
more advantage car. The T Ford was well made however nobody forced those
people to use another car.

Just my thought,

Cor

**Relaxin** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

[color=blue]
> The datatable has a lot of extra's above the recordset by instance a
> dataview, with can show you data in a lot of ways. This newsgroup is not
> the part to show all advantages from a datatable above a recordset.[/color]

A recordset is comparible to a datatable (in your example) if you are going
to use the dataset to create the dataview.
You could also use other oledb components and functions to sort, filter,
etc.. to create the same "dataview" "like" data.
So you are making a mute point here.
[color=blue]
> And not to tell that there are only advantages in some cases can the
> standard optimistic concurrency in my opinion be a disadvantage, however
> modern disconnected use makes pessimistic concurrency in my opinion very
> hard to do and should only be done when it is really needed[/color]

And where are you coming up with this "pessimisti c concurrency", I have
always used optimistic concurrency.
In fact OLEDB allowed you to use SQL Servers rowversion (1 field) as a
method to update a record.
ADO.NET will use a WHERE clause of all of the columns within your SELECT
statement.
This is a very inefficient why to update a record!

[color=blue]
> To select one or more datarows from a datatable you can use the
> datatable.selec t
> You can as well find a row in the datarow collection in a datatable by
> using a datarowcollecti on.find
> Or get a selection by using the dataview.rowfil ter
> Or get a position of a datarow in a dataview by the dataview.find
>
> You can use as well of course to narrow your datatable the different
> select where clauses.
>
> Maybe you can say it was more simple with the recordset because it had not
> all those possibilities.[/color]

Your statements are "trying" to limit my argument to the recordset, but you
have used a DataSet, DataTable, DataView and a DataRowCollecti on!!
Lets be fair about this, OLEDB and ADO.NET are both comprised of classes and
the classes are designed to work together, except MS has removed alot of
functionality from some of the ADO.NET classes.

"Cor Ligthert" <notmyfirstname @planet.nl> wrote in message
news:OcadZzY7EH A.1396@tk2msftn gp13.phx.gbl...[color=blue]
> Relaxin,
>
> Probably is your major mistake although you are not writing it, that you
> compare a dataset with a recordset, what is not the case. A recordset is
> comparable with a datatable.
>
> The datatable has a lot of extra's above the recordset by instance a
> dataview, with can show you data in a lot of ways. This newsgroup is not
> the part to show all advantages from a datatable above a recordset.
>
> And not to tell that there are only advantages in some cases can the
> standard optimistic concurrency in my opinion be a disadvantage, however
> modern disconnected use makes pessimistic concurrency in my opinion very
> hard to do and should only be done when it is really needed
>
> To select one or more datarows from a datatable you can use the
> datatable.selec t
> You can as well find a row in the datarow collection in a datatable by
> using a datarowcollecti on.find
> Or get a selection by using the dataview.rowfil ter
> Or get a position of a datarow in a dataview by the dataview.find
>
> You can use as well of course to narrow your datatable the different
> select where clauses.
>
> Maybe you can say it was more simple with the recordset because it had not
> all those possibilities. The same as people who went from the T Ford to a
> more advantage car. The T Ford was well made however nobody forced those
> people to use another car.
>
> Just my thought,
>
> Cor
>
>[/color]

**Cor Ligthert** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

Relaxin,

I get more and more the idea that you don't know what is a dataset,
datatable, datarow, dataview and/or a datarowview in ADONET. Can you explain
what they are in your opinion.

Because when we talk about different things it is hard to make a discussion.

Cor

**Relaxin** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

I know EXACTLY what they are, but since you asked for it.

The DataSet contains 1 or more DataTables.
A DataTable contains 1 or more DataRows.
A DataRow contains 1 or more DataColumns.
A DataView is a subset and/or sorted view of the DataSet.
I'm still unsure what the purpose of the DataRowViews is, but I know
DataRowView.Fin dRows returns it.

Like I mentioned earlier, I have created my own components to handle things
the way they should be.

I'm mainly venting because I would have expected a better design from MS,
but I guess if you(most people in this NG, I assume) haven't seen anything
other than MS, you wouldn't have anything to compare it to.
So of course you would think that this design is great.

Give Borland a try when you get a chance, you will see a hell of a design.
You can tell that Borland tools are Developed By Developers for Developers.

MS is designed for cash only!!

"Cor Ligthert" <notmyfirstname @planet.nl> wrote in message
news:OqAvBUZ7EH A.3416@TK2MSFTN GP09.phx.gbl...[color=blue]
> Relaxin,
>
> I get more and more the idea that you don't know what is a dataset,
> datatable, datarow, dataview and/or a datarowview in ADONET. Can you
> explain what they are in your opinion.
>
> Because when we talk about different things it is hard to make a
> discussion.
>
> Cor
>[/color]

**Cor Ligthert** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

Relaxin
[color=blue]
>I know EXACTLY what they are, but since you asked for it.[/color]
[color=blue]
> The DataSet contains 1 or more DataTables[/color]
references 0 or more
[color=blue]
> A DataTable contains 1 or more DataRows[/color]
references 0 or more.
[color=blue]
> A DataRow contains 1 or more DataColumns.[/color]
A DataRow references 0 or more Items described by the columncollectio n from
the DataTable
[color=blue]
> A DataView is a subset and/or sorted view of the DataSet.[/color]
The DataView is a view on a datatable not on the Dataset (as you
consequently state) which has filters and sort parameters in it. Every
DataTable contains one Dataview named DefaultView.
[color=blue]
> I'm still unsure what the purpose of the DataRowViews is, but I know[/color]
A DataRowView is a view on an single datarow however as well on other class
objects
[color=blue]
> DataRowView.Fin dRows returns it.[/color]
I don't know the DataRowView.Fin dRows method so I do not know what you mean
with this.

I don't think that your first statement about EXACTLY is very correct.

Just my thought,

Cor

**J. Buelna - Houston, TX** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

"Relaxin" <me@yourhouse.c om> wrote in message
news:eP8eDTW7EH A.4028@TK2MSFTN GP15.phx.gbl...[color=blue]
> It is just me or has MS created some of the worst ways to access and
> display
> data?
>
> You can use a DataSet, but if you want to sort or filter the data to must
> use a DataView which is created from a DataSet.
>
> But, if you sort by using the Grid (clicking the header) you can no longer
> use the DataSet (or maybe the DataView, if that is what you are using) to
> locate the record that the user has selected!!
>
> You have to write code to get the current position...this should just be a
> property!!
>
> Also, can someone explain to me why does the FindRows return
> DataRowView...w hat can you do with a DataRowView, I haven't figure out a
> way
> to load this data into a new DataView or a DataSet (if there is a way,
> please explain it to me). It seems that the FindRows should have just
> return a new DataView!!
>
> I understand why all of the necessary data access components are broken
> out
> into many different parts, but why not ALSO build a component that
> encompasses all of the components and use that as an "enhanced DataSet"
> that
> can also be used as a Datasource to the grid and other components.(Thi s is
> something that I have already done for myself.)
>
> Maybe it's because I'm coming from Borland and expect top notch
> development
> tools/comopnents...wh ere there VCL Framework and Data Access components
> were
> THE BEST!!!
>
> But I had to leave Borland because their management said that they were
> killing the Borland C++ Builder (BCB) product about 6 months ago. But,
> they
> just recently announced that they had a change of heart and will now
> support
> BCB.
> That's a little to flaky for me, so I jumped ship and moved to MS.
>
> But with what I have seen in VS.NET (C#), I might have to talk my chances
> with Borland.
>[/color]

Hello Relaxin,

I'm sorry, I don't have time to go into details. Here are some references:

Microsoft® ADO.NET Step by Step
http://www.microsoft.com/mspress/books/4825.asp

Microsoft® ADO.NET (Core Reference)
http://www.microsoft.com/mspress/books/5354.asp

Professional ADO.NET
http://www.amazon.com/exec/obidos/tg...books&n=507846

It would be good to learn and fully understand ADO.NET on an academic level
before trying to use it in a commercial project. Unless your employer
allows you to learn the as you go.

ADO.NET is not perfect, but there was a lot of thought that went into
architecting it and rest assured that there is a solution for most of the
problems you'll run into.

J. Buelna - Houston, TX

**Michel van den Berg** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

Why don't you try using LLBLGen Pro (www.llblgen.com). I find it much
easier to use then the default way of data access.

Have a nice New Years Eve,

Michel van den Berg

Relaxin wrote:[color=blue]
> It is just me or has MS created some of the worst ways to access and display
> data?
>
> You can use a DataSet, but if you want to sort or filter the data to must
> use a DataView which is created from a DataSet.
>
> But, if you sort by using the Grid (clicking the header) you can no longer
> use the DataSet (or maybe the DataView, if that is what you are using) to
> locate the record that the user has selected!!
>
> You have to write code to get the current position...this should just be a
> property!!
>
> Also, can someone explain to me why does the FindRows return
> DataRowView...w hat can you do with a DataRowView, I haven't figure out a way
> to load this data into a new DataView or a DataSet (if there is a way,
> please explain it to me). It seems that the FindRows should have just
> return a new DataView!!
>
> I understand why all of the necessary data access components are broken out
> into many different parts, but why not ALSO build a component that
> encompasses all of the components and use that as an "enhanced DataSet" that
> can also be used as a Datasource to the grid and other components.(Thi s is
> something that I have already done for myself.)
>
> Maybe it's because I'm coming from Borland and expect top notch development
> tools/comopnents...wh ere there VCL Framework and Data Access components were
> THE BEST!!!
>
> But I had to leave Borland because their management said that they were
> killing the Borland C++ Builder (BCB) product about 6 months ago. But, they
> just recently announced that they had a change of heart and will now support
> BCB.
> That's a little to flaky for me, so I jumped ship and moved to MS.
>
> But with what I have seen in VS.NET (C#), I might have to talk my chances
> with Borland.
>
>
>[/color]

**Relaxin** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

What I need is a connected resultset within the confines of a DataSet.

My database is full of images, and as you could imagine, this is a painful
process when they are all loaded to the clientside.

Anyone with any knowledge in this area?

"J. Buelna - Houston, TX" <jbuelna-not@microsoft.. .yet.com> wrote in message
news:OT$wqrb7EH A.3336@TK2MSFTN GP11.phx.gbl...[color=blue]
>
> "Relaxin" <me@yourhouse.c om> wrote in message
> news:eP8eDTW7EH A.4028@TK2MSFTN GP15.phx.gbl...[color=green]
>> It is just me or has MS created some of the worst ways to access and
>> display
>> data?
>>
>> You can use a DataSet, but if you want to sort or filter the data to must
>> use a DataView which is created from a DataSet.
>>
>> But, if you sort by using the Grid (clicking the header) you can no
>> longer
>> use the DataSet (or maybe the DataView, if that is what you are using) to
>> locate the record that the user has selected!!
>>
>> You have to write code to get the current position...this should just be
>> a
>> property!!
>>
>> Also, can someone explain to me why does the FindRows return
>> DataRowView...w hat can you do with a DataRowView, I haven't figure out a
>> way
>> to load this data into a new DataView or a DataSet (if there is a way,
>> please explain it to me). It seems that the FindRows should have just
>> return a new DataView!!
>>
>> I understand why all of the necessary data access components are broken
>> out
>> into many different parts, but why not ALSO build a component that
>> encompasses all of the components and use that as an "enhanced DataSet"
>> that
>> can also be used as a Datasource to the grid and other components.(Thi s
>> is
>> something that I have already done for myself.)
>>
>> Maybe it's because I'm coming from Borland and expect top notch
>> development
>> tools/comopnents...wh ere there VCL Framework and Data Access components
>> were
>> THE BEST!!!
>>
>> But I had to leave Borland because their management said that they were
>> killing the Borland C++ Builder (BCB) product about 6 months ago. But,
>> they
>> just recently announced that they had a change of heart and will now
>> support
>> BCB.
>> That's a little to flaky for me, so I jumped ship and moved to MS.
>>
>> But with what I have seen in VS.NET (C#), I might have to talk my chances
>> with Borland.
>>[/color]
>
>
> Hello Relaxin,
>
> I'm sorry, I don't have time to go into details. Here are some
> references:
>
> Microsoft® ADO.NET Step by Step
> http://www.microsoft.com/mspress/books/4825.asp
>
> Microsoft® ADO.NET (Core Reference)
> http://www.microsoft.com/mspress/books/5354.asp
>
> Professional ADO.NET
> http://www.amazon.com/exec/obidos/tg...books&n=507846
>
> It would be good to learn and fully understand ADO.NET on an academic
> level before trying to use it in a commercial project. Unless your
> employer allows you to learn the as you go.
>
> ADO.NET is not perfect, but there was a lot of thought that went into
> architecting it and rest assured that there is a solution for most of the
> problems you'll run into.
>
> J. Buelna - Houston, TX
>[/color]

**Relaxin** · Jul 21 '05, 08:05 PM

Re: Database access sucks!

ok, 0 or more.
I guess you found the loophole you were looking for.

Have a great day!

"Cor Ligthert" <notmyfirstname @planet.nl> wrote in message
news:%23Lk24Zb7 EHA.3708@TK2MSF TNGP14.phx.gbl. ..[color=blue]
> Relaxin
>[color=green]
>>I know EXACTLY what they are, but since you asked for it.[/color]
>[color=green]
>> The DataSet contains 1 or more DataTables[/color]
> references 0 or more
>[color=green]
>> A DataTable contains 1 or more DataRows[/color]
> references 0 or more.
>[color=green]
>> A DataRow contains 1 or more DataColumns.[/color]
> A DataRow references 0 or more Items described by the columncollectio n
> from the DataTable
>[color=green]
>> A DataView is a subset and/or sorted view of the DataSet.[/color]
> The DataView is a view on a datatable not on the Dataset (as you
> consequently state) which has filters and sort parameters in it. Every
> DataTable contains one Dataview named DefaultView.
>[color=green]
>> I'm still unsure what the purpose of the DataRowViews is, but I know[/color]
> A DataRowView is a view on an single datarow however as well on other
> class objects
>[color=green]
>> DataRowView.Fin dRows returns it.[/color]
> I don't know the DataRowView.Fin dRows method so I do not know what you
> mean with this.
>
> I don't think that your first statement about EXACTLY is very correct.
>
> Just my thought,
>
> Cor
>[/color]

Database access sucks!

Database access sucks!

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment