Another way/better way of designing this page/table?
1. I have a page with some fields like first name, last name, address, city, etc.
2. Some fields are required and some aren't.
3. On the page, I want to have 2 buttons; "Save for later" and "Save & Submit"
4. I created two tables with the same fields. In one table (for Save-for-Later"), I have the fields as nullable.
In the real table (table for Save & Submit), I have the required fields as non-nullable and the non-required ones as nullable.
So, I have 2 tables. I wonder if this is a good design. If I want to display ALL the data (complete and incomplete) in a table, I have to go to two tables and get the data. Maybe I need a "complete" flag?
Maybe I just need one Save-For-Later table and have all the fields as nullable. When user clicks on "Save & Submit".... I insert the row from one table to the other?
Any ideas or is my orig design idea is good?
2. Some fields are required and some aren't.
3. On the page, I want to have 2 buttons; "Save for later" and "Save & Submit"
4. I created two tables with the same fields. In one table (for Save-for-Later"), I have the fields as nullable.
In the real table (table for Save & Submit), I have the required fields as non-nullable and the non-required ones as nullable.
So, I have 2 tables. I wonder if this is a good design. If I want to display ALL the data (complete and incomplete) in a table, I have to go to two tables and get the data. Maybe I need a "complete" flag?
Maybe I just need one Save-For-Later table and have all the fields as nullable. When user clicks on "Save & Submit".... I insert the row from one table to the other?
Any ideas or is my orig design idea is good?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, Scott. I created 2 tables.
I thought about having one table with the required fields as non-nullable and populating them with a predetermined "dummy data" if user clicks "Save for Later" but I don't think that's a good idea. I'll go with 2 tables...one for real data and one for when user saves for later.
I can pull data from both tables and have a column in the grid to show which records are completed and which ones aren't.
I thought about having one table with the required fields as non-nullable and populating them with a predetermined "dummy data" if user clicks "Save for Later" but I don't think that's a good idea. I'll go with 2 tables...one for real data and one for when user saves for later.
I can pull data from both tables and have a column in the grid to show which records are completed and which ones aren't.
ASKER