>>>>>My question is perhaps more for myself, but I am interested in other peoples point of view regarding this. >>>>> >>>>>I have a formset containing 2 forms. The second form is activated when a value doesn't exist in a combo box or when it is double clicked. Ideally what I would like to do is pass the unknown value ( or .text) to the second form and return either .t. or .f. based on the correct updating of the table ie a new record inserted correctly not cancelled out of. >>>>> >>>>>I guess the only way to do it in this manner is to dump the formset and call the second form directly, this way a value can be returned also. >>>>>Or I could just use some variables which would be available within the formset. >>>>> >>>>>What do you do? >>>>> >>>>>Cheers >>>>>John >>>> >>>>Kill the formset and use a modal form with the TO clause. Better yet, why not just a messagebox asking the user if she wants to add the value to the list? >>> >>>My favorite technique is to use the doformretval procedure which is used in the Tas Traders app. It's a simple way to use class-based forms. I like to call them 'pop-up' forms. >>> >>>It uses the tsformretval class in the tsbase library. I've made some pretty meaty changes to mine (I didn't bother to subclass, I just made a copy and begain hacking away), but the Tas Traders example is pretty simple. >> >> >>Thanks guys! >> >>I did feel that getting rid of the formset was the best solution, but was reluctant if there were other ways of utilizing it. >> >>Alas poor formset... I knew him well... (well almost well, more of a casual aquaintance... in fact, the more I think of it... the less I liked him! Alas poor formset... *not*) < G > >> >>Cheers >>John > >I missed this thread, sorry. Just one word to defend formset. Actually, you asked a question what interface is preferred modal or modeless. The fair answer is following: modal interface (which exludes formset) is simpler, modeless interface is richer. In regard to particular question how one formset.form can check another formset.form: what's the problem here if you have formset properties which can be addressed easy from any form. Formset specific is that you should shift code from Form.Init events to Form.Activate events, i.e. each form 'analyzes' current application situation when it gets focus. I have many other things say, but maybe it too late...

It's never too late to hear from someone of your ability and experience!

Some of the first stuff I've read about VFP5 was that the formset was a resource hog, had bugs (never described) and was better replaced by the PageFrame, which was easier to code. So, I've never used the FormSet. I know alot about the bugs in PageFrame, however. How would you compare the two approaches? I have one app in which property info appears on page1, personal income info on page2 and access controlled info and utilities appear on page3. How would switching pages compare to switch forms in a formset, in regard to speed, length of object identifies, etc...?