>>Personally, my work qualifies depending on your definition of n-tier. I use business objects and data brokers but they generally are within a VCX internal to the app so it's virtual n-tier but physically 2-tier.
>
>Sure John! Remember, n-tier design is two sided: logical and physical. Yours might be only logical but it would be just little more work to convert it into physical if/when you want or need to.
>
>Just curious before I setforth on my n-tier journey, how much more work, in your opinion, was/is needed in your projects? I know there's more coding involved since word "bound" (e.g. controls) becomes somewhat meaningless. In addition, have you tried physically separating the UI from BO (separate EXE/DLL), and if so, what is your experience?

John,

It is very easy to go to the next step. Simply publish your business classes as activex servers by making them OLEPublic in a dll. If you have desinged your form class so it has a property for the name of the business class to create, you only have to change the value in that property from "MyClass" to "MyDll.MyClass" and it is now running the ActiveX server class instead of the native VFP class.

BTW, there really isn't any distinction between a "logical 3-Tier" and "physical 3- tier" design. Design is design and implementation is implementation. If a design is 3-tier, then it is 3-tier regardless as to how you choose to implement it.