Kendall's reply to Bob:
>As I recall, one of the turnoffs for formsets goes back to VFP3 when people were doing automatic conversions from 2.6. The VFP form conversion wizard defaults to using formsets which is the equivalent of a 2.6 screen set. But it created a formset on every form converted whether it was in a screen set or not. Including the "Formset" in containership code like Formset.Form1.oThis.oThat meant additional typing and added another layer of objects to traverse.

The advice then was to move to private datasessions and to the new data environment capablities of forms in VFP3, which made parent/child relationships much easier to setup. Formsets really don't buy you much and carry some baggage. The native DE functionality of forms in VFP really don't need an additional formset layer to work great right out of the box.<

I veiw the additional layer of containership provided by the formset object as an advantage over forms. We implemented Doug Hennig's strategy for error handling in which the ERROR method of the offending object would travers up the object hierarchy and delegate to the first object that contained code in it's ERROR method. Since formsets contain all forms, we could place our error handling logic in the ERROR method of the formset. Any error in any object on any form in the set delegated to the same handler logic. Nice...

It's great MSFT gave us so much to talk about... kind of like politics and/or religion :)

Best,
Jeff



Jeff