Design Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi, I have been reading so much on Datasets and designing using layers, that
I am so confused I don't know what to do.

I am trying to build a Timesheet tracking application. Most applications
seem to use n-tier design now, so I would like to try and implement this.

Anyway, I have a Data Access Layer in which I have generated typed datasets
using the designer. I have created multiple datasets, with groupings of
tables that I think I will need to work with.

I then have a Business Layer which accesses these databases, roughly based
on what this series or articles talks abou
http://msdn.microsoft.com/library/d...l/aspnet_tutorial02_businesslogiclayer_vb.asp

I am a bit confused how to implement something fairly basic.

Say on Login, I need to verify the user against valid users (in tblUsers), I
also need to hold and frequently refer to the users access priviliges for
different screens, so i know what they should or shouldnt be able to see.

To check the user login, and store the details, should I have a business
object (User) to store I datatable? even though all I really want is to get
one row? ie the user who logged in?. Or should I have the business object,
simply call the datalayer, return all the fields that I want and store them
in properties? (seems a waste, however storing a whole datatable seems a big
overhead).

I also need to be update the user with last logged in date and time etc.

I tried just using datarows, however, to check for an update I needed a
datatable...

I also need a maintennance screen for an admin person to add, update and
delete users and their priviliges. SHould this be a seperate business object
that returns a datatable to the presentation layer.?

Any direction appreciated.

thanks
 
Hi, I have been reading so much on Datasets and designing using
layers, that I am so confused I don't know what to do.

I am trying to build a Timesheet tracking application. Most
applications seem to use n-tier design now, so I would like to try and
implement this.

Anyway, I have a Data Access Layer in which I have generated typed
datasets using the designer. I have created multiple datasets, with
groupings of tables that I think I will need to work with.
Click to expand...


Take a look at LLBLGen - it generates data objects which are much easier
to use (and more applicable) than the standard typed Datasets + datatables.
 
Take a look at LLBLGen - it generates data objects which are much easier
to use (and more applicable) than the standard typed Datasets + datatables.
Click to expand...

Any other advice that doesnt involve using a 3rd party app?
 
Back
Top