Yes, storing in a Session or Client struct is your only option. Earlier versions of CF would lose sessions set before a CFLOCATION as well, so if you're on CFMX or something, use JavaScript location.href = "C.cfm" for the redirect to get around that.
---------------------------------------- From: "Eric Cobb" <[email protected]> Sent: Wednesday, March 23, 2011 10:58 AM To: "cf-talk" <[email protected]> Subject: Persisting query data across cflocation Given the following scenario, what would be the best way to persist the data across the cflocation call? I have page A, which includes page B, which does a cflocation to page C. Query results returned in page A need to be available in page C. Since we're doing a cflocation, which starts a new request, storing the query results in the request scope doesn't work, and a query result set can't be passed as a url variable in the cflocation tag. Is storing the query results in the session scope on page A, then retrieving it on page C my best option? Either that or calling the query on both page A and page C? I was really hoping there was an easier way (like storing it in the request scope!), but I can't seem to figure it out. -- Thanks, Eric Cobb http://www.cfgears.com Help me make a difference this summer.http://bit.ly/i8dJvQ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:343227 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
