I handle this by checking wether the Insert is going to overwrite and throw an error... if the userID is the same however I branch to an update statement instead of an insert statement.
At 06:42 AM 8/14/02, you wrote: >:> Here's a method I use: instead of writing to the database on every new >:> page, just drop the entire form structure into every page as hidden >:> fields. > >I thought about it, but this particular application has close to 650 fields, >and I was a little worried about carrying that many from one page to the >next. Would have been a hell of an insert statement at the end of it all. >Made more sense to write each page. > >JavaScript history approach, along with instructions not to use the back >button while filling out the form, seems to d the trick for this particular >application. > >Has anybody ever "measured" the amount of variables that could be carried >from one page to another? Surely there's a limit somewhere before the server >starts to bog down or cause problems. > >Thanks, > >Les:> > > ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
