Duplicate temp tables for holding 'inprocessregistration data?
Posted on 2005-04-08
I'm designing a database that will register and later use client business information.
The web sign up process is rather long, three pages, that involves uploading images, inputing credit card number, business discriptions and so on.
I need to creat a session manager that will let them return sever times to finish the process.
(close their browser,next day and so on).
My question is, is it better to have 'duplicate' tables to hold this tempory data (some would never be completed), and another for completely registered clients or one that has a field for 'not registered'?