I don't have many controls on the pages I need to remove. Add to this the fact that I have code that processes all the controls on the pages which I don't really want to change to add in the extra container if I where to delay instantiation.

So I think returning .F. in the Init will probable be my best bet.

Thanks for the help.

>>Thanks Nadya as I said in my original message I was trying not to have to do the delayed instantiation bit.
>>
>>But I agree that the controls appear to be loading even if the page isn't so I may have to go that route after all.
>>
>>I guess that returning .F. in the controls init is already to late and it will have loaded?
>>
>
>Returning .f. from controls Init should be enough, but how many controls do you have on each page? If few, you can probably return .f. from controls Init, otherwise I would prefer delayed instantiation.
>
>>>>Thanks for the replies but I think I answered it myself, I've just returned .F. in the init() of the appropriate pages.
>>>>
>>>>>Caroline
>>>
>>>I think, controls on the page still go through their Init even if you return .f. in page Init.
>>>
>>>You can design container with page controls for all pages and add these containers in the run-time. That's called delayed instantiation and I used this technique in few projects...