#1 Business Objects do not have to exist If and Only If there is a database
counter part. Case #1, UnitTests.
#2 Your backend datastore could change, thus layers give you a better way
to maintain your code.
You can look at an example here:
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!139.entry
(code is downloadable).
There is a MS "bird's eye view" article I reference. Read and reread that
article several times. Bookmark it, and in a few months, go back and reread
it.
"Savvoulidis Iordanis" <Sa*****************@discussions.microsoft.comwrot e
in message news:79**********************************@microsof t.com...
Why separate the Data Access Layer (DAL) methods from the Business Layer
(BL)methods of an object ? Why not have them inside the object itself,
since
it's going to save its own data, using its own methods?
Is it just a matter of avoiding clutter of the code? Or try to avoid big
objects in memory? Won't the DAL object consume memory by itself anyway?
Any reasonable explanation is appreciated.
TIA
Iordanis