table design issue
I have an web application. User wants to do the following task every year in the web interface.
(a) save / submit data any number of times for multiple records in a given year in the UI.
(b) approve all records once in a year in the UI..... once approved.... records can not modified by user....will become read only in the UI.
my problem:
Should I make two tables ? one for save/submit for multiple records entered by user and other for approve by user ?
OR
Should I make one table ? save/submit/approve for multiple records all in one table ?
OR
how do I design my table to do this ?