Happy Monday all. I am doing a next-n search interface for my project. I have done these before but they usually only have one or two variables for the query, and I usually use URL parameters for these. This particular form can have up to 20 different fields that the user can use to do a search depending on what they are looking for, so of course I am passing all of the form variables into the dynamic query. problem is, when I click on the next button, or one of the page numbers on the bottom, the query is expecting the form variables. I can CFPARAM them, but then when I click on next or a page name, I get all of the record instead of the filtered ones since the form variables are not empty. I tried using query caching but that does not work either. So what would be the best practice for this? Put all of the form variables into a session variable then use the session variables for my filter on next/back clicks? I thought of using URL variables, but there is a limit to how many characters you can put into a URL so that will not work.
Thanks, -- Bruce Sorge "I'm a mawg: half man, half dog. I'm my own best friend!" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:267954 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
