Nick,

Thanks. I will try this.




>>
>>What would be a good technique to use to logically relate 3 or more forms this way? It would be good if they could share the datasession. For now I am not using forms as classes, as I am not familiar (yet) with the techniques for constructing the data environment manually, but ultimately I would like to go in that direction.
>>
>>Any and all suggestions would be appreciated.
>>
>>TIA
>
>Hi David,
>
>No, tabless pageframe is not a VFP 7 feature. You can have it even in VFP 3. It is just a pageframe with .Tabs = .f. You may switch the pages in code as needed. So you could logically combine the controls from 3 forms into 3-page tabless pageframe. Since there will be just one form for them, they will share the datasession. It is probably a good idea for this case to use the delayed page instantiation. Which means that the controls will be placed into container subclasses, and these containers will be added to the corresponding page only when the page is activated. This saves time for the form instantiation. Only the controls on the active page will be instantiated when you run the form first time.
>Delayed instantiation is used as a standard feature in some commercial frameworks, for example CodeMine.