hi, i am making an asp.net front end to a sql server database. The
system will become quite large and will focus on different 'areas' or
information

When the user logs in they get to a main navigation page where they can
manage database information which is relevant to them. They can open a
page to input and manage their risks and hazards, or open another page
to input and manage their incidents, or yet another page to enter shift
summaries

What i would like to know is how i should go about designing the
datasets in .net 2.0

Should i have one dataset and add all the table adapters to that, or
would i be better to have one dataset for each 'area' of management, ie
a dataset for the risks tables, a dataset for the incidents tables, and
another one for the shift summaries?

There will be a total of about 10 or more different information they
will be accessing

Hope this made sense

Thank you in advance for any assistance

I would go with one dataset for each major group of pages.
What I mean by this is that you create a dataset for your member's
section, in this case containing 3 tables. There's no point having one
dataset per datatable.

Naturally you would only be returning the rows relevant to the member
into the dataset.
What kinds of numbers of rows are you talking about per member? And how
do you want the information displayed?

hi

thank you for the response

i would say that for each page, ie if they to to their incidents page
they will never have more than a list of 100 records returned, and
normally much less, then they can retrieve the details for each one
from that list

it is on an intranet

in the end there will be about 10 tables, aside from the lookup tables

risks and hazards
incidents and reportable events
shift summaries
audit recommendations
health and safety tasks
contracts
departmental complaints
restraint events

i just wondered whether i have one dataset for each table, or combine
all the table adapters in to one dataset

thank you again for your advice, i really appreciate it


Steven Nagy wrote:
Show quoteHide quote

Well as mentioned before, its silly to have one dataset per table. A
dataset is designed to be a collection of tables so really you should
keep your logic together. For the tables relating to the user's items
(risks, etc) then have one dataset.

thank you

that makes sense to me now

Steven Nagy wrote:
Show quoteHide quote

Validating textbox w/ Cancel button
Delegate et al
Mdi Form Validating
?Delegates and Interaces - similarities/differences?
checking MP3 license
VB.NET ComboBox _SelectedIndexChanged
ComboBox in DataGrid
Treeview problem
How to find files in a directory
How to compare two identical tables in VB.NET + MS Access