D
dwight
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
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