>>>>>>{Updated} - Solved it
>>>>>
>>>>>Do you really need to be adding these things at runtime?
>>>>>
>>>>>I find it *MUCH* easier (as someone else suggested) to add as much as possible at design time and then just control visibility or change attributes at runtime.
>>>>>
>>>>>This was cake in VFP. ASP.NET is a giant leap backward from VFP.
>>>>
>>>>IIRC the Visible property in ASP.NET doesn't really have anything in common with same VFP property. In ASP.NET with Visible=false the object in question simply won't exist.....
>>>
>>>Correct. If I want something to not show on an ASP.net page I set visible to false and it does not render at all.
>>
>>So why make a comparison between VFP and ASP.NET in this instance?
>
>Because in VFP you can do NewObject/RemoveObject and it's much harder in ASP.NET.

RemoveObject wouldn't make much sense in a browser application ?
And what's hard about

form1.Controls.Add(Page.LoadControl("SomeUserControl.ascx"));