>
>When I said class-driven, I really meant the data-side. I always write the app itself based on classes, but if you could bind to data directly to controls, it's far quicker than going the 3-tier route.
>

There really isn't any reason you need to throw out binding to cursors/tables/views when moving to n-tier. It's not required (inside of VFP). Let your business object do the updates of the cursors. Add methods that can convert from/to cursors for external/non-VFP apps (SCATTER and Collections in VFP 8 makes this incredibly easy, or any of the XML stuff). The Mere Mortals framework takes this approach (using cursors for VFP, other data access methods for other environments).

There is a difference between logical n-tier and physical n-tier. Most of us are only doing logical n-tier development. That is, we've "logically" broken apart our code into separate layers. The idea is that we can swap out and/or move these layers around w/o affecting other code. The side effect of this is that you could move some of these layers off to difference machines and your code would still work (physical n-tier).