I removed all tables that are not specifically related to the EAV definition. I also removed the endorsement tables which are also EAV but would just complicate the definition.
-- data
tblVariableDataHeader = the header for the policy.
tblVariableDataValues = the data for the EVA fields. One row per field
--- definition
tblProduct = the header for each product type
tblField = all the variable fields. Field types are -- "Text";"Date";"Currency";"Number";"Percent";"Memo". ControlTypes are -- "Combo";"TextBox";"Checkbox". ComboDataSourceName = the name of the query to populate the RowSource of the combo.
tblProductFields = the fields associated with a particular product. This is the source of the append query. When a policy is being quoted, the variableDataHeader is created and the ProductID is used in the append query that copies the tblProductField definitions to tblVariableDataValues where they will eventually be filled.
tblDocument = the documents associated with a product.
tblDocumentFields = the fields associated with a document.
To add a new policy type the user would do the following:
1. Add row to tblproduct
2. Add new fields to tblField
3. Add fields to tblProductFields - copy options are available to reduce data entry
4. Create necessary Word documents with bookmarks
5. Add documents to tblDocument
6. Add fields to DocumentFields
7. Ask me to create any new queries needed for the combo lists. I couldn't let the user create database objects. If I were to do it again, I would put these queries in a table rather than making them permanent and then create them as temporary querydefs on the fly.