>>>Nadya,
>>>
>>>I share your concerns about duplicating a container across multiple pages in a page frame. But dynamically reconfiguring tab order on a page by page basis seems complicated as well.
>>>
>>>I'm leaning towards Craig's suggestion of adding my container to a special page class and then using the MemberClass* properties to reference this specialized page class.
>>>
>>>Thanks for your help,
>>>Malcolm
>>
>>Yes, it's up to you to weigh downsides of each approach. I would probably go with Glenn's/mine idea to avoid the overhead. On the other side, if that navigation class is light weight, Craig's suggestion would be easier to implement.
>
>OTOH, that would be each page having an instance of the container - that's multiple containers then. But if the idea is to have all the things on the containers show the same thing, that can be achieved by binding all the controls on it to same controlsources, and refreshing them in .uiEnable(). Sounds simpler, and also solves the tab order problem.

I'm not sure, I get what you mean here. I think, Malcolm was talking about navigation bar container. We had the same class at my prev. job called navstand. In our case we always put it on the form beneath the pageframe.