Hiya JimB ---

>No, what I am suggesting is that n-tier is not necessarily a more complex solution. Once the classes exist it really takes no more or less effort to make an app n-tier than 1 tier.
>
>I think that n-tier often gets a bad rap as being complex when it is not.

It probably depends on the a) scope of application and, b) skills of the developer. I'm not raining on n-tier, I firmly believe that an architecture should be as complicated as required for the application but never more so.

JVP in his response brought up interesting points that I find myself agreeing with insofar as complexity and scope issues.

As to "virtual n-tier" I think we all do it. That single-tier app I alluded to in an earlier post has business service classes, a quasi-data services class (handles queries and mass post operations but not basic I/U/D -- I have bound controls).