> care more about speed or memory usage. If I have a formset with three > simple forms, and I expect the users to go back and forth a lot, I might > load 'em all and just show them and hide them. If the formset has 15 > forms, and some of these have 15 page pageframes and a couple of grids, > each with dozens of controls, and embedded pictures, and will be run on an > old machine, each form might be better off being CREATEOBJECTed and > RELEASEd as needed. Maybe this can be further elaborated with some .ini setting upon install time, so if there is something like [hardware] machine_class=up_to_16_meg So if the app decides the machine it runs on is a good old minimum RAM machine, it CreateObjects, otherwise it loads it all and plays hide and seek with the forms. Something like If gsMachine_Class="up_to_16_meg" oForm2=CreateObject("Form2Class") else oForm2.show() endif In much the same manner the formset.init would load minimal or full set of forms. How does this sound for a deployment strategy? > I seem to have made a new verb: to createobject - I createobject, you > createobject, he/she createobjects, we createobject, y'all createobject > (for Texans) they createobject. :) I thought verbs were restricted to OLE... and then, you may be right. I've even heard of "teekaybeeing" from PDP-11 TKB (task builder, i.e. linker).