Design Issue

[Mike]

I am designing an application with business objects and data access layers.
I currently designed a data access layer that will encompass 3 business
objects data access methods. Does it matter that I combined the DALC? The
reason I did this is because the DALC only retrieves data no updates and the
DALC describes the 3 business objects as one entity. I guess I could match
the DALC and make one business object however there is certain logic
(methods/properties) unique to each business object. Any ideas?

Thanks

[Cowboy \(Gregory A. Beamer\)]

It shouldn't. If you are trying to be more purist, you can create a data
layer for strongly typed datasets and their fill methods and create a
generic layer for database. This is what Paul Sherriff advises in his
webcast (you can see an archived copy at
http://www.microsoft.com/usa/webcasts - go to archived webcasts). He has an
interesting method of setting up the business objects, deriving them from
System.Data.DataSet. Rather interesting.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************** ********************
Think Outside the Box!
************************************************** ********************
"Mike" <nospam> wrote in message
news:%2********************@TK2MSFTNGP12.phx.gbl.. .

I am designing an application with business objects and data access layers. I currently designed a data access layer that will encompass 3 business
objects data access methods. Does it matter that I combined the DALC? The reason I did this is because the DALC only retrieves data no updates and the DALC describes the 3 business objects as one entity. I guess I could match the DALC and make one business object however there is certain logic
(methods/properties) unique to each business object. Any ideas?

Thanks