Well instead of doing a database call every page - I just stored variables in a session scope.
Once they finish the 4th step - they then get written into database because they are valuable now. I set sessions to expire after 30 minutes.. so if they got side tracked and came back - the form was all there. I personally think doing it that way allowed me to do a few other integrations quicker. For example - I have a flash application that has a quick contact form, filling that out - user gets an email that points them to my multi-page form. Data collected from flash app is available to them once they get to the form, even with them never having been there. This I think was easier through the sessions. Again - after the last step - I then purge the sessions - write some fields to database and a few important ones to cookies - and it works quite well. A few others had suggested sessions too. hth jay Rafael Alan Bleiweiss wrote: > Why not post the contents to the DB after each page? I do this and it > allows me to retain the input for those sites where the visitor has the > rights to come back again later. Post once per page, and no worries. I > track which page was completed in the DB and check for a "AllCompleted flag. > > If they don't come back after x days, it gets wiped. > > Are there disadvantages to this? (always looking for more efficient methods) > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
