Form variables should be fine in most instances as long as you
remember to htmleditformat() your hidden fields... If you want a more
"seemless" user experience, you might consider storing submitted form
variables in a session structure and then using those to pre-populate
the form if the user returns, thus, if a user walks away for a few
minutes or moves around the site when they come back to the form,
their informatino will still be there waiting for them to comlete it.
<!--- form page --->
<!--- make sure there's a session structure to hold form variables
--->
<cfparam name="session.savedform" type="struct"
default="#structnew()#">
<!--- prepopulate the form fields with the saved info
<cfset structappend(form,session.savedform,false)>
<!--- action page --->
<!--- save form data to the session scope --->
<cfset structappend(session.savedform,form,true)>
hth
s. isaac dealey 214.823.9345
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
> Hello,
> I have an application that using many form post (hidden)
> to pass values
> between templates, as the data is maniputlated and used.
> Some have maybe
> 75 form vars. I am wondering if this is the best way to
> pass these vars.
> It seems to work fine, but would a session (75 of them) or
> somethign
> else be a better way to use pass this information. Someone
> has mentioned
> an object but I have yet to look into it and have not used
> them before.
> Any help would good. I just want to give users on slower
> connections the
> best possible experience. Maybe form vars are the way to
> go, it does
> work ok.
> Jeremy
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
