>What are the pros and cons of directly "tying" a form's fields to their data source property vesus creating a "middle level" object that stores the values in each of the form's fields and then has the methods to "insert," "modify," "discard," "rollback," etc. Using the Microsoft 3-tier model, I am inclined to create a business level (or middle level) object to store a form's data and then act upon that data as appropriate.
>
>What are the various opinions about this?
>
>
>Sincerely,
>
>Rob

My opinion is that ControlSource could be omitted in most cases. Actually, MS created it to allow simplification for form creation process (drag-and-drop from DE). It's really great for unexperienced users, but VFP itself is not for unexperinced folk. Also, people using this 'easy' way immediately get into 'buffering' trap which is not easy. I think 3-tiered strategy is good and extendable: you can use either form level custom methods or move them onto class level with all data manipulation power (at least here Fox is still the best) in your hands.