For anyone interested in this (and I'm guessing there aren't many <g>), I solved the problem.

My bad ... I missed an important piece of the puzzle when I translated to C# from VB. There was a property that needed to be put in my UserControl base class and I just flat-out missed that little tidbit. I got desparate enough to email the author of the article and he was kind enough to help me. Anyway, it's working perfectly now.

~~Bonnie


>Sorry, I haven't tried the code in the article.
>
>If the problem only happens on the first click, I would guess it has something to do with state and/or postback...I realize that this is a loooong shot.
>
>>Hector and anyone else who may be interested,
>>
>>>>I ran accross this article http://www.fawcette.com/vsm/2003_04/magazine/columns/aspnet/ and thought that you might be interested on it. <
>>
>>I know I replied to you that I found this article a few days earlier and it was what I ended up using and it worked perfectly ... but now I'm banging my head up against the wall again. I've found a problem with a C# version of this (the article had VB code, which I translated to C#). It appears to have a slight problem with handling the Click event of a button which is placed on the UserControl. It doesn't fire the Click event the first time the button is clicked, but works fine every time after that. Check out the article ... it really is a cool solution for dynamically adding UserControls. Has anyone attempted this with C#?
>>
>>~~Bonnie
>>
>>
>>>Bonnie,
>>>
>>>I ran accross this article http://www.fawcette.com/vsm/2003_04/magazine/columns/aspnet/ and thought that you might be interested on it.
>>>
>>>Although it seems that you've found the solution for your problem. Anyway, better late than never :)
>>>
>>>