HTMLForm database best practices: RDBM, normalization, required/optional fields, adding/removing fields
===

I work for a college that has multiple types of forms.
We are converting our old system (form data -> email) to a more efficient system (sql) for many reasons: reporting, speed, mailbox limitations, etc.

I understand normalization and sql commands just fine... I'm hung up on these:

1. required vs optional fields (null or separate table)
2. changes to the form (adding/removing fields and how it's reflected in the table design)
3. 1:1 form to table ratio or 1:N form to table ratio
4. If 1:N, will this affect the reports of each form?

Do you know of a site/book/article/tutorial that gives great information on how to store form data in a database that touches my concerns?

or, could you describe what is a "tried and true" method?

I'd like to aim for 3rd or 4th normalization if possible.


----------

My initial thoughts are:

 1. create a table, "application," that has fields for all required (permanent) data.
 2. create a table, "application_extra," that has the fields: application_id, field_title and field_value

but would this be okay for reporting?

thanks!