>First I need to clarify some syntax. I will use scxform to refer to the form file (the .scx file) and objform to refer to the form which is an object in the scxform. I read in the early advisories on VFP that you should use a formset in the scxform and put all the objforms you will need for a specific task in it. If you reuse an objform make it a class. When you do this and include the class based on the objform, suprisingly, you don't save anything on the size of the scxform. It simply copies the class into the scxform. While you gain all the encapsulation/inheritance stuff which is great you don't save on loading time.
>
>The question to challenge convention is should you divide your complex scxforms into smaller scxforms that call each other/pass info to each other etc so you can improve loading time as you only load the formset with the objforms you need. Then if you need another scxform it will load resulting in more waiting while the task is ongoing but much less upfront.
>
>I don't think this is the way most people do things but was interested in discussion on the pros and cons of doing this.

For my understanding Formset is necessary in a case we have couple logically related forms (usually appearing and working together). Otherwise we can open multiple forms separately. I have particular problem with form loading time. Some forms containing OCXs load too slow, therefore I open them when starting application, hide them on background and invoke when it's necessary and release when application quits.