Larry,
A different way without popups would be to store the information in
viewstate (the client computer) and use panels for the lookup. You could put
your main form being filled out into a panel and then swap out the lookup
panel(s) and the form panel as needed with the panel's Visible property.
--
Sincerely,
S. Justin Gengo, MCP
Web Developer / Programmer
www.aboutfortunate.com
"Out of chaos comes order."
Nietzsche
"Larry Charlton" <La***********@discussions.microsoft.com> wrote in message
news:7F**********************************@microsof t.com...
Is there a way to arbitrarily persist and restore a page state? For
instance: I'm half way through filling out a page and I come accross a
field
that I don't know which value should be placed in it. What I'd like to do
is
have a lookup button. In the code for the button click event, I'd like to
persist all the information on the form (say to a database or file),
redirect
to another page passing a persistence ticket.
The "called page" would note which page called it, allow me to lookup the
value I'm interested in and "return" to the previous page, noting that I'm
returning.
The original page would at some point early in page life cycle determine
that it had been "returned" to, and set the page state to the earlier
persisted version, possibly adding in "returned" information (assuming the
lookup wasn't canceled) and then redisplaying the page focusing the next
control (or if canceled the current control).
Could be there's a better way to do this or something similar in .net and
I'd love pointers to either the problem above or a different approach
that's
maybe more .net ish.
Pop-ups I'd prefer not to do.
