> 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?

I have mortals and am going throught the manual. I am using it as a way to learn codebook/mortals, etc but I am doing some things that I may want to keep for my final app. The manual has the control source set to local view fields. Specifically see page 20 of the Jump Start:
3. Set TextBox.ControlSource to "v_Staff.cName"

I am new to codebook, so hopefully this isn't off too far, are you saying that the control source should be a property of the form? I thought that would be a better way of separating the second tier also as I want to eventually advertise my product as a true 3-tier/client server, etc. etc.

Since I am coding things now, what do you suggest that I do to avoid a complete rewrite when VFP98/Mortal 6.0 comes out?

If I set the control source to a property, where should the property be updated? In the form refresh?

Are you going to put some information on the Internet so we can begin to prepare?