>Also, placing user interface controls within the business object container makes reusability difficult because if you need to drop a business object on a different form to access its functionality you end up dragging along unneeded user interface controls with it.
>
>With the advent of Visual FoxPro 6, business objects created as ActiveX Automation Servers are finally becoming a viable option. When we release our VFP6 version of the Codebook for Mere Mortals framework, we will provide a clean, scaleable path to true three-tier architecture.

Along the same lines, it's not really correct (in terms of 3-tier development) to reference your views as control sources for your controls, is it? Shouldn't they be accessed via properties of your business object? Unless you've already written your apps to provide everything through properties wouldn't you need to rewrite most of your business objects to provide this functionality? Or, would your class views instead be mapped to a ADO/OLE DB/??? object instead?