>This on-the-fly delayed control creation in page.Activate event is great optimalization idea. I will give a try next time. You should make a patent on it! :-)
>
>bb

He-he :) I'm not the originator of this idea, otherwise I would make millions on it :)
>
>>>>Hi Dorin
>>>>
>>>>The pageframes are better. You can addobject the controls to the pages when the user first activates them. This is called delayed instantiation. It can make your forms load faster, since not all controls will instantiate until they are needed.
>>>
>>>A disadvantage IMO of delayed instantiation is that you can't use the form designer for those objects, unless you use classes of course.
>>
>>You design these objects visually on the form, then use Save as class and save them as a container class. And then just add this container in the Page.Activate. I use this technique a lot and it speeds the form's instantiation a great deal.
>>
>>>
>>>The performance argument is new for me with regard to vfp. I've heard it before from a VB developer. I've been told that in VB the equivalent of thisform.refresh() will also act upon all hidden pages. In vfp this is not case.
>>
>>If you have lots of code in Init, Load, Refresh, you may see performance degradation...
>>
>>BTW, long time ago John Koziol published VFP Do and Donts. I am wondering, where this material now?