1. Caching either the data or the entire rendered output of the select box in the application scope. A custom tag is another option.
2. On the server, in the fuseaction handling the form submission, you can have an if block that checks for validation failure. If validation is ok, perform a relocate to whatever page comes next. If validation fails, just use a <do> to re-run the same fuseaction that displayed the form. Have some code at the top of the dispaly to check for error messages and display them if they are present. Hope that helps. On 6/6/07, CFMX DEV <[EMAIL PROTECTED]> wrote: > > Sorry for the OT, but I am not having any luck with the Fusebox5 mailing > list on Yahoo nor anything on Google. > Yes, I hit those before posting here. > > 1. What is the best way to have a select list setup compiled and reused on > various pages? > Ex: State select list compiled and called on many display pages. > At first I thought it was best in the fusebox.ini.cfm file calling: > v.stateList where the view circuit would call the dsp_state.cfm file. > But that threw an error. > > 2. When using dsp pages to show a form, then sending it to an action file > and performing some server side validation, if the SSV > failes, I want to go back to the form page, display the form and values > entered as well as message regarding the failure. I am using > client side and server side validation in case the end user has JS > disabled. > > TIA!! > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Macromedia ColdFusion MX7 Upgrade to MX7 & experience time-saving features, more productivity. http://www.adobe.com/products/coldfusion?sdid=RVJW Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:280325 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
