Hi David,

You go to each page in the pageframe and save all of the controls on that page as a class (it ends up as a container with the controls in it I think). The you programatticly add the Class to the page when the page is first activated.

That way the form does not have to instantiate all the controls when first loaded.

The entire procedure is listed in the VFP help under "Optomizing Applications"

hth

>What is the save as class technique? It sounds like creating the form as a form then saving it as a class, vs. creating the class and then creating a form from that?
>
>
>>That's probably where the problem is. Sorry, but I would suggest you to use SaveAsClass technique for the pageframes. :) If you didn't do it yet, check also some resize classes in Files Section, may be it will help.
>>
>>>The slowest form has around 130 controls on several page frames.
>>>We have built our own vcx for control resizing, so most of them do have 30+lines of code in the init. I'll look into the Coverage Profiler and see what it shows.
>>>
>>>>Joe, how many controls do you have there? Do they run a lot of code in their INITs?
>>>>Also, if it uses views you may try to set their .NoDataOnLoad = .t.
>>>>You may also try the Coverage Profiler to figure out the possible bottlenecks.