aspx thread: DataView vs DataSetView vs ... When to use what?
I'm struggling to figure out ADO.NET and which objects would be best for the
project I am working on. I am hoping that someone can either shed some light
on this directly for me or point me in the direction of some good articles.
I have read much of the docs in the ASP.NET SDK and VS.NET, but I'm still a
bit mystified about when to use what.
Here's what I'm trying to do. It's pretty basic: I have a set of tables that
contain all the data defining a hospital staff member. There's quite a lot
of varied data, so we used 7 tables to contain it all (e.g., Personnel,
PersonnelPhone, PersonnelAddress, PersonnelHealthSpecialty, and then tables
to link these together so that many-to-many relationships could be
established). I need to develop an area of the hospital site that allows a
person to do the following:
1. Search for staff members and return results in a datagrid with a
hyperlink column that takes the user to a details page.
2. Add a new staff member.
3. Edit and delete existing staff members.
Pretty basic stuff, really. But ASP.NET is so new, as is ADO.NET, that I
it's not yet clear how best to proceed.
I have many questions all related to the question of how best to set this
up. Would it make the most sense to grab all the Personnel data into one
DataSet and then use a DataView as the datasource for binding given my
particular needs for that control? Or should I use a DataSetView? (I don't
understand the difference between the two.) And let's say I need multiple
filters for the data displayed in the search results DataGrid (e.g., each
staff member can have up to 6 different phone types and up to 9 different
health specialties. In the results I need to show ONLY the work phone and
the primary health specialty. This would require two RowFilters. Is this
possible? Or do I create a TableSetting for a DataSetView and then use a
RowFilter within this to accomplish all the filtering I need?).
I am conceptually missing the big picture on all these new ADO.NET objects.
Perhaps if I could read a detailed document or tutorials about it, and how
each is applied to any given situation, it would make sense to me. Is there
anything out there like that? If not, would anyone care to write a tutorial
(Doug Seven? Steve Schofield? Susan Warren?) or a white paper on this? I
think it might benefit a lot of people. I sure with there was a good WROX
ADO.NET book coming out soon.
Thank you for any help you can give,
Patrick Barnes