The better architecture would be: DAL: Data Access Layer GetRecordset ( recordsource *sql string* or *exec storedprocedure*) Static, clientside, batchoptimistic, for insert, update,delete
ReadRecordset( recordsource *sql string* or *exec storedprocedure*) static, clientside, readonly, for read only access, firehose recordset --------------------------------------------- BLL: Business Logic Layer GetCustomer Getcustomer(ID) GetAccount --------------------------------------------- happy programming M Tanveer ----- Original Message ----- From: "Andreas Håkansson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 28, 2002 1:43 AM Subject: [DOTNET] Data Access Layer > I'm making a very small 3-tier application to try > out some concepts. Imagine I have the following > design > > (1)BUSINESS LAYER > Customer > Account > > (2)DATA ACCESS LAYER > CustomerDB > > > Now the Customer class maintince a list of account > objects internaly, which you can access through the > Customer object using various methods. > > Would the CustomerDB include methods such as > GetCustomer, GetCustomer(int id), GetAccounts(int customerID) > etc ? > > Thus ecapsulating everything needed to create a fully > functional customer object in the business layer.. > > -- > Andreas Håkansson > Student of Software Engineering > andreas (at) selfinflicted.org > > In a world in which we are all slaves to the laws of gravity, > I'm proud to be counted as one of the freedom fighters. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
