>>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.
>
>yes, having the forms seperated and not all loaded when the app start is better IMHO
>
>I go even further from what u do:
>what I do is have a sigle formset object whithin all the forms and toolbar will live
>I have my forms saved as objects (probably vcxforms in your terminolegy) and they are instanciated as needed (and added to the formset) same goes for the toolbars
>the formset class I built can be set to either load with the last forms that were opend or just with the main toolbar (depending on users settings)
>
>another thing u can do is instead of closing a form just hide it
>and have ur program just show it when the form is needed again (this ofcourse depends on your memory setup and type of your app.)
>
Definetly, the hide and not release and reinitiate is the way to go. I like the idea of your "blank formset" if you will which loads forms as needed. Doing this you really need to obey all the encapsulation rules however, because your never quite sure of the environment so everything needed must be kept within the class. While this is good style I will be the first to admit I often violate it. Do you have problems referencing objects across forms? Do you use variables to pass info or do you check to see if a needed form is in existance if not init it and then reference it?