Hi Kevin

I can understand your uses but there is still an aspect that I am wondering about. In VFP if I opened a number of forms with a lot of databound controls it could be a slow process if the network was slow etc. So I put all the controls used on a form into a container, one container per form. Then to speed up the load time I only added the container to the form when it was activated. This meant that only the first form had any databound controls which made the load time for the forms faster because only the first form had any controls. The other controls were not added until their parent form was activated.

So I am still wondering about this form load time with databound controls. Is it still a good idea to put all the form's controls into a container and only add the container at run time to reduce the load time when several forms are opened at once? If the load time is not an issue then I might just put my databound controls on a form at design time.

Thanks
Simon White




>I am still wondering whether this is necessary in .NET or whether it is a VFP specific issue I should just drop.
>
>Hey, Simon,
>
>Just wanted to jump in, it's a good question, not just a VFP thing (and Bonnie gave the answer, you subclass your individual winform controls and then drop the ones you want onto a usercontrol [container] according to your needs).
>
>When I went from VFP to .NET, I recreated many of my containers as .NET usercontrols, such as a common OK/Cancel button set that I wanted to drop on forms, a standard set of related controls for user report options.
>
>Other examples might be a simple 'mover' container that has the two listboxes and buttons to add/remove,etc, or even a 'grid container' that has a grid and a few buttons and textboxes for searching the grid.
>
>I look at it more as a need/requirement from an overall standpoint, with the development tool providing the means to do it.
>
>Hope that helps...
>Kevin