General Page Design Question

[Tim Tafflinger]

Hello,

I'm developing an application with one parent table and 12 child tables.
The parent table is patient information and the children contain such things
as lab results, medications, emergency room visits, etc. I'm trying to
decide how many gridview and sqldatasource controls is too many for one page.
I like the way the user interface works with everything on one page where
they can select a parent record from a gridview control then with a drop down
select the one child they want to view or edit. I would have a gridview and
sqldatasource for each child table and simply use the visible property to
show the one corresponding to what they select from the dropdown. I have it
working with 3 at the moment and it works fine but that's only 3 and it's on
my local machine. I've never put 12 of each on a page so I don't know what
issues I may encounter. Good idea? Bad idea? Would it be better to break
it out into 12 separate pages? Other suggestions?

 

[Tim Tafflinger]

Hi Mark, I'm only showing 2 gridviews at a time. One is the parent table
and the other is the one showing the child information they choose from a
dropdown. All the other child gridviews are set to invisible. When they
make a new selection I set the visible property of the one being viewed to
false and the visible property of the one selected to true.

So you don't think having that mamy gridviews on one page will be an issue
as far as stability, response, etc.?

I'll look at implementing a DAL. Thanks!

 

[bruce barker]

as long as you turn viewstate off, otherwise the page size will be too large
for performance.

-- bruce (sqlwork.com)