Thanks for the reply.

Eventually I ended up using a serializable class, which holds the entered
data, and is stored in the session when the user navigates away from the
page. In the Page_Load subroutine, I use a try...catch...end try statement
to try and convert the session object into it's correct type. If the object
is found, the controls are populated, and the user sent to the next step in
the process. If it errors, the object is not set, and the user is at step
1.

Mun



"Kevin Spencer" <kevin@SPAMMERSSUCKtakempis.com> wrote in message
news:u0dehdZODHA.1624@tk2msftngp13.phx.gbl...
> Instead of redirecting, use Server.Transfer to get to the form handler.
The
> original Page class called will be in the HttpContext as the "Handler"
> object. You can also add your ViewState items to the Context.Items
> Collection prior to transferring, in order to see them in the other page.
>
> HTH,
>
> Kevin Spencer
> Microsoft FrontPage MVP
> Internet Developer
> [url]http://www.takempis.com[/url]
> Big things are made up of
> lots of Little things.