[FX.php List] Best Practices for Forms

[Bob Patin]

Yes, I totally agree; that's how I do it. I create the record and  
then edit it on successive pages. In the case of a shopping cart, I  
use "temporary orders" table for orders anyway; the actual invoice  
record isn't written until an order is successfully paid for.

In my dealings with large registration systems for conferences, etc.,  
I've found that applicants make far less mistakes in their  
applications when each form asks for less information. I always  
separate credit card submission information, for example, and  
normally separate other things, for example:

If a conference has several types of attendance packages, I usually  
give the applicant these choices first, then go into other options,  
then personal info (name address, etc.), then finally payment.

The other useful thing about this is that testing is easier when  
there aren't 100 different fields on a single form!

Bob Patin
Longterm Solutions
bob at longtermsolutions.com
615-333-6858
http://www.longtermsolutions.com

   CONTACT US VIA INSTANT MESSAGING:
      AIM or iChat: longterm1954
      Yahoo: longterm_solutions
      MSN: tech at longtermsolutions.com
      ICQ: 159333060


On Jul 17, 2006, at 1:42 PM, Gjermund Gusland Thorsen wrote:

> option 2 is the way to go
>
> Look up: session_start()
>
> Do FMNew
> keep the -recid of current record in _SESSION variable
> and do FMEdit on the next pages submitted.
>
> ggt667

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.iviking.org/pipermail/fx.php_list/attachments/20060717/e7ac178f/attachment.html