Re: Session variables problem

From: Joe Fallon (jfallon1_at_nospamtwcny.rr.com)
Date: 12/02/04 

Date: Wed, 1 Dec 2004 23:59:34 -0500

Simon,
I use Session to store my search criteria classes all the time.
Then on the results page I pull the criteria out of session, and use it to
build the SQL command to get the results which are displayed in the grid.

If the user retunrs to the Search page, I pull the crtieria class out of
session and populate the search controls with the data they last entered.
They can then change some settings or push the Clear Form button to re-set
all the values to their defaults.

This sounds exactly like what you are trying to do (except you use a
Structure instead of a class which is not very different.)

I guess I don't see what the problem is that you are having. This technique
works well for me.
Can you please elaborate a bit? 

-- 
Joe Fallon
"Simon Matthews" <SimonMatthews@discussions.microsoft.com> wrote in message 
news:A935A4AB-6BF9-436A-9C24-C68BF625F179@microsoft.com...
>I am having issues with the right way to architecture the following (using 
>c#
> asp.net):-
>
> The question I have is how best pass the collected data from one web page
> for use in another.
>
> The question I have is how best pass the search criteria from the first 
> page
> to the second. The search criteria exists as a structure and is filled 
> when
> the user presses the 'Search' button on the first page.
>
> 1. Present an asp page for collecting user search criteria
> 2. Show grid with results of search after querying SQL
>
>
>
> If I use the session to store it, then this causes problems as the session
> variable is overwritten on a second search by the user, but a couple of
> presses on the back button of the browser will get you to a page expecting
> different criteria in the session from earlier which is no longer there.
>
> ViewState seems no good as it only works on postback and the above issue
> would still cause a problem.
>
> I do not want to pass the search criteria in the address line as this is
> messy and allows the user to change and view it.
>
> I beleive you can also use Server.Transfer but I think this would have a
> similiar issue with the data being available long-term.
>
> Any pointers as to the correct approach to this would be most welcome.