Mike Copeland wrote on 2011-07-08: > I could be completely wrong, but my understanding was that formSETS was > an attempt at providing a way to control an applications forms, and also > to provide some communication between forms...kind of a supra-form, or > form-parent object reference. > > formset.form1.textbox.value=1 > formset.form2.textbox.value=formset.form1.textbox.value > ?formset.form2.textbox.value would then show "1" > > But, regardless, they were always a lot of trouble and best avoided at > all costs. > > Mike
Mike, Back in the Windows 3.1 days, they would help reduce the number of files you had open. They shared the same DataEnvironment. Move a record pointer in a table in form2, it moves in form1 All common methods and properties on the FormSet object. Yeah, sounds like something that might have a use. I never could figure a real world example. It's easy to write bugs in the code since things from the other forms isn't always accounted for. I agree with the others. It's best to stay away from them. Much easier to deal with individual forms. Tracy Pearson PowerChurch Software _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
