Bhavbhuti,

No, you can't remove the contained objects of a container subclass at design time.

You can RemoveObject() them at runtime, or set their .Visible = .f.

But that begs the issue that the class design might be non-optimal if you wholesale want to rip it's guts out at the point of use. Perhaps it could be redesigned to conditionally add objects as it instantiates, or pulled apart into other classes that can be aggregated together better.

>There is a form class on it is the instantiated container class.
>The container class maybe in another vcx has controls on it.
>
>Your suggestion still valid?