>You were right. Formsets are a REALLY bad idea. Stop now before things get too nasty. Rethink how things need to work and use forms.
>
>>I've never worked with formsets (thought they sounded like a really bad idea), but now have need of one for a special purpose. I can't seem to find any way to add a new method to a form contained in the set. The menu Form>New Method adds the new method to the set, not a contained form. Tried hacking the VCX file Methods field, then recompiling the form, but that failed as well. The reason for doing this: some classes, like an address container class, have calls to "thisform.mymethod" that exist in certain form subclasses, but not in the form in the set added with menu Form>Add New Form. I presume that a call to thisform.mymethod will not get bumped up hill to thisformset.mymethod. Is there some way to add methods to a a form contained in a formset?

Maybe I should ask the other half of the question then: I have a customer that insists they want a scrolling form (another really bad idea, in my opinion--but I can't talk them out of it), but we need a small section at the top of the form containing key information to be fixed (not scroll) while the rest of the form scrolls. Formsets, at first glance, seemed like a solution. But now I'm thinking maybe two separate forms linked with common DatasessionID and physically tied through the MovedEvent method. I don't know, what do you think? Seems like a lot of coding is going to be needed either way.