"What-a-Tool" <Fr***********************@cox.net> wrote in
news:SEB9b.64780$Zw4.48304@lakeread03:
Data Tables - Interesting things!
Been cramming through Ado.Net - Step by step since I decided to try my
hand at this project (just a personal learning project) using ADO.
Just got to the section on Data tables and data viewers, and I see
your point. By the way - I did post this on the ADO news group. I
didn't get a response. Theres more action in this group, and the
subjects are related, aren't they?
m.p.d.l.vb seems to have more traffic than the ADO.NET group. Anyhow,
yes, ADO.NET and VB.NET are related.
However, ADO and ADO.NET are two totally different things. ADO is
Microsoft's older Data Access layer while ADO.NET is the the new version
for .NET. ADO.NET has significant changes and has hardly any resemblence
to ADO.
I suggest that you bind objects to a data table instead of an array
because DataTables provide much more rich functionality such as Sorting,
Views, etc. Also, when binding to a DataTable to a control, you can
easily specify the displaymember and valuemember columns. I believe if
you want to specify displaymember/valuemember columns with an array you
need to create a new class object and that takes much more code.
Arrays are probably easier on memory, but the advantages of the datatable
are definately worth the tradeoff in my mind.
--
Lucas Tam (RE********@rogers.com)
Please delete "REMOVE" from the e-mail address when replying.
http://members.ebay.com/aboutme/coolspot18/