Welcome to my world. I stepped into a place where wizard-produced code, formsets, and binding directly to tables and locking the DBC in multi-user applications are commonplace. The only thing worse is the underlying code. Don't even get me started about SET DELETED OFF...
Now that our main app is running in SQL, we're migrating everything else to it and I can re-write the applications properly. Lou -----Original Message----- From: profoxtech-boun...@leafe.com [mailto:profoxtech-boun...@leafe.com] On Behalf Of Kent Belan Sent: Friday, July 08, 2011 3:29 PM To: profoxt...@leafe.com Subject: RE: FormSets and PageFrames I am working on a project now that was started in FPW 2.6 and many of the screens were built with the wizard. Then the project was run thru a converter to VFP6 and then updated to VFP9. When I have to work on one of the old forms, I just throw it away and start over. It is a mess of formset's and wizard code ... Not fun -----Original Message----- From: profox-boun...@leafe.com [mailto:profox-boun...@leafe.com] On Behalf Of Tracy Pearson Sent: Friday, July 08, 2011 6:14 PM To: profox@leafe.com Subject: RE: FormSets and PageFrames 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 [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com 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/010801cc3e55$801788b0$80469a10$@com ** 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.
