Yup.
But, IAC, one of the problems with going
physical n-tier from the get-go if the client is not screaming for it is that very often it's hard to model the business process because the client is not used to thinking about how his stuff can be automated.
In many cases I have had the client sign-off on DFDs, ERDs, and other models just to completely throw a wrench into the project when they saw how it was actually going to work.
So I guess what I am saying is that it's easier to design and implement an n-tier system when you have a fully matured, automated business process ...which usually starts as a simple monolithic app that evolves over some time.
>>Doesn't surprise me. And why would it change? The single-tier model is still the most efficient (expense-wise) for small to medium clients with a compelling business need.
>
>Only the first time around...
>
>Of course there's that learning curve <bg>...
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05