This is all nice, but let me tell you, from a recent experience..
I just finished up a "registration" form, that worked in steps..
you know.. fill in information, submit, get presented the next set of input fields..
This presented some very interesting situations..
Granted, I did it all in one document, like I normally handle forms with PHP.. but I found myself faced with a some very interesting issues..
All -in-all I opted to insert the data into the database at the end of each step.
That way I didn't have to carry copius amounts of hidden form fields.
I also chose to use a cookie in conjunction with a hidden field.. to solve any "non-cookie" users.
So far it appears to work nicely.. my problem really came from trying to decide "where" to start the database entry process.
If anyone knows of a way to prevent a document from being stored in a viewers browser history.. I would certainly like to know.. that would solve other potential problems
Low Cost Hosting and Web Development.