>Bob,
>
>I'm not sure if this is a real question or not? I had that *BG* in my reply.
>
>Assuming this is a real question is though...
>
>Yes, it's more maintainable, and more complex too right? The maintability is generally easier because a decent O-O design would let you get pretty decent reuse and therefore higher quality code because each reuse would tend to shake out the bugs at the lower levels of the class hierarchy.

>The increased complexity comes because of the interfaces between the tiers. And now you have code in 3 layers to potentially have to debug for any given problem that arises.

df,

One thing that I'd like to point out that hasn't been mentioned is that you don't end up playing every developers' favorite game: "Where's the code?":-)

This especially applies to business logic if it's been stored in a business object.

No argument that overall such an arrangement is more complex, but if properly done it will be easier to maintain, as well as what you mentioned, more re-usable.



>>WAIT!!!!
>>
>>Isn't layered (logical n-tier) code supposed to be MORE MAINTAINABLE?
>>
>>>3-tiers = 3 times the debugging *bg*
>>>
>>>>I agree 100%. There are a number of layers that apply. It's a good illustration of all 3 tiers having rule obligations. Table, business, and UI logic is required, IMHO. Any one piece missing may cause problems down the road.