>Thank you all for the replies. We figured out the solution which may be of common interest:
>
>For each page of the page frame, create a container class that contains all of the controls for the page.
>When the page activates, add the container. When the class de-activates dispose the object.
>Of course, there is a small penalty of instantiating the object each time you click a new tab, but in our case at least, it's not a big problem.
>

Congratulations on arriving at the answer that is often given for this problem. This will work in many situations, but in others (like Bruce mentioned) it won't. Eric had a good point too- if your interface gets to the point that it becomes a resource hog, then maybe it is time to rethink the interface- because a complicated interface for the computer often means a complicated interface for the user.