<div>
I agree completely with jrb1. That's the best way to handle that situation.<br />

</div>


I agree completely with jrb1. That's the best way to handle that situation.


<div>
Thank very much for your answer, appricate it.
</div>


Thank very much for your answer, appricate it.

<div>
<div class="content wysiwyg-content">
 &nbsp; I'm designing a database that will register and later use client business information. &nbsp;<br />
The web sign up process is rather long, three pages, that involves uploading &nbsp;images, inputing credit card number, business discriptions and so on. <br />
<br />
&nbsp; I need to creat a session manager that will let them return sever times to finish the process.<br />
(close their browser,next day and so on).<br />
&nbsp; <br />
&nbsp;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'?<br />
<br />
<br />
<br />
&nbsp; <br />
<br />
&nbsp; 
</div>
</div>


   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'?



  

  

Duplicate temp tables for holding 'inprocessregistration data?

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.