"Business Objects" and the DAL

I *still* can't get my head around this.

In designing a basic n-tier application, what exactly is the relationship
between the "Business Objects" and the "Data Access Layer"?

In the past when I have attempted to make an n-tier application, business
objects end up basically being a representation of the data from the
database. I see terms like "Business Rules" and "Business Logic" and I just
don't understand what that is? I have a couple questions I hope someone can
answer for me:

1) Should the Business Objects make calls to the DAL? ( IE:
BusinessObjectCollection BusinessObject::GetCustomers() calls DataSet
Dal::GetCustomers() ) then the Business Object builds itself up from
the results of the DAL DataSet, or should there be a third class that gets a
DataSet from a DAL, then passes it to a business object to digest?

2) Can someone please give me 1 or 2 examples of a Business Rule and
Business Logic? Tons of articles make reference to the two, but finding an
example is next to impossible.

Spinning my wheels, I really hope someone can shed some light on this.

Thanks for reading,
Steve Klett



.

Relevant Pages

  • Re: UI and BL Interface
    ... I am designing a 3 tier application. ... I have seen examples that the UI creates and new business object ... layers, requiring a communications layer like a web service. ... business objects from its controls' events, ...
    (microsoft.public.dotnet.languages.csharp)
  • UI and BL Interface
    ... I am designing a 3 tier application. ... input and populates the BL to store into a db. ... about design an interface that the UI interfaces between ... I have seen examples that the UI creates and new business object ...
    (microsoft.public.dotnet.languages.csharp)