>>>Hi Michel ---
>>>
>>>>There are other problems too : if you do not want the form to
>>>>even initialize depending on the value of some of the parameters,
>>>>am I right in saying that the only way to do it inside a formset
>>>>is to have the form initialize as HIDDEN and then either un-hide it
>>>>or release it depending on what the parameters are ?
>>>>
>>>
>>>I don't think you can prevent the form from Initializing at all but you can hide it. I'm not that familiar with Formsets but an idea has occurred to me: What if you created the Forms as standalone classes (remove them from formset) and then used "AddObject" where appropriate to dynamically add them? I have no clue if this would work but......???
>>
>>It will. It's actually the way to work with formsets.
>
>Edward and John,
>
>I'm interested in your two replies. John, from your reply it would
>seem you have not worked much with formsets. Any reason why ?
>
>Edward, on the other hand you do seem to have worked with formsets.
>Any advice on when formsets are appropriate, their advantages,
>and inconveniences ?
>
>Thanks.
>Michel.

I worked with formsets in VFP3 (because top form is not available there). They provide good way to implement OO application hierarchy. I used to start application with formset containing toolbar, DE and generic methods (but no forms). Any form is inctanciated from a class and manipulated by Formset.Add/RemoveObject().