Nick Baker wrote:

> A session variable holds through 2 pages then is not recognized on the 3rd
> page. Going back to the other pages and refreshing that page shows the
> session variable to be valid.
>
> Any ideas?
>
> Thanks,
>
> Nick
>
> More specifics
>
> 1. Execute the following query
>
> <cfquery name="Session.SrchResults" datasource="BusDB" Maxrows=160
> dbtype="ODBC">
>
> This same query will be used on each of the following pages, only
> displaying different variables based on users selection. Below is the query.
>
> <cfoutput query="#Session.SrchResults#" startrow=#Session.CurrentRow#
> maxrows=1>
>
> On the 3rd page it throws the following error.
>
> "Element SRCHRESULTS is undefined in SESSION"

That's potentially an awful lot of data to be storing in the session.
It could be that CF is saying "Bugger me! There's a lot of stuff here.
I'm dumping it".

In other words, try using query caching instead. It'll give you the
effect you're looking for without screwing the pooch with the session
scope.

--
Keith Gaughan -- talideon.com
The man who removes a mountain begins
by carrying away small stones...
                          ...to make place for some really big nukes!
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to