>>I am creating an app that uses 5 screens (forms). Typically
>>in the past I would create individual forms and call them
>>with "do form xxxxxxx". I am now wondering if a formset is
>>a better way to work. Then I would change the "visible"
>>property as I need a certain form displayed. The reason
>>I don't think I like the "do form" method is that it
>>seems that the data environment has to be set up for each
>>form. With a formset I could do that once. I'm no expert
>>so I would like some input.
>
>Formsets are kind of passe now, and theere is little reason to use them any longer (though I still have an older app with some, I've been removing them as time permits). The way I avoid formsets but get around the common DE problem is simple - I almost never use DEs for data common to many forms. Some ways to manage common data is either in an app object, or use a top-level to do it, that's the way I always do it now...

What I don't understand is... if I create the DE in a top-level form...
I cannot access the data in other forms that are of type "show in top
level form". I add a field to the form and the control source is blank
unless I add a DE of it's own.