Business Object Question

[Tim]

I am wondering what other developers think about combining business objects
and data access layers components? Here is my design:
UI-UIprocess/controller-BO/DACL-DAhelper-DB

[Dave Veeneman]

> I am wondering what other developers think about combining business
objects

and data access layers components?

Not sure what you mean by 'combining'-- your design seems to put the DALC in
a separate layer from the business objects. To answer the general question,
I would strongly recommend separating the DALC from the BO. That way, if you
switch to/from Access,SQL Server, Oracle, MySQL, and so on, you only have to
modify and retest the DALC. In other words, you open a much smaller can of
worms by changing your data access platform-- a day's work, instead of a
week's, with much lower risk of uncaught bugs.

[Jeffrey Tan[MSFT]]

Hi Tim,

Normally, we recommand you implement your application as 3 layers.
Because binding the business layer and data access layer will reduce the
flexibility of your application. Usually, the business layer is the most
frequently changed layer.
But these all depand on the logic and design of your application.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.