Neil, without getting too much into the specifics of your question, let me
pass along the following advice:

Don't do anything weird.

Consider that tens (or hundreds?) of thousands of developers have tested the
"normal" way, but that you may be the only person trying it the "weird" way.

I found this out the hard way. I just got a complicated control to work
properly - by methodically removing anything "weird". For instance, rather
than play desperate games trying to switch between two sets of controls at
runtime by tricking ASP.NET into loading their ViewState at the proper
times, I now create _both_ sets of controls and let ASP.NET handle their
ViewState in the "normal" manner. Not surprisingly, Microsoft tested the
"normal" case, and it works!

--
John Saunders
Internet Engineer
[email]john.saunders@surfcontrol.com[/email]


"Neil Kimber" <neil.kimber@flytxt.com> wrote in message
news:%23%23K6Z2PUDHA.1576@TK2MSFTNGP12.phx.gbl...
> I understand the reasoning for ProcessPostData Second Try.
> For controls to be correctly populated with PostBack data they must be
> created dynamically no later than Page_Load() event. However, is it
possible
> for me to create controls dynamically after Page_Load() and then cause the
> PostBack data to be correctly loaded programmatically? Could I have
> something like:
>
> MyUserControl.LoadPostBackData();
>
> Any suggestions?
> Thanks,
> Neil
>
>