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

I'm also familiar with THAT error handling strategy too, which can also be implemented in a base form class without the use of a formset. That strategy also defers to a global error handler if no error method code is found while traversing the inheritance chain. Whether that chain is nested in a formset or inherited through other subclasses doesn't effect the ability to implement it. I don't see any advantage to using formsets there Jeff, just a different approach. Separate from formsets, the granularity and control of error handling will change for the better in VFP8 with the Try/Catch implementation. You might not need those formsets after all, JK!!!

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

Agreed, the product is rich. But, you still haven't convinced me that formsets are THE
way to go, just another way to go.