How to structure a database to take input and assign applicable questions appropriately
I am creating a database that will feature the following information and need to accomplish the following goals. Information: Customer Name e.g. "Otter's Wash Co" Customer's Project Name. One customer could have many projects. e.g. "Fur Shur Wash" Project Elements with checkboxes to add them to the report. Elements may or may not apply to all projects, but the answers will be specific to each separate project. e.g. "Bus Wash" ---Some project elements would need to have follow-up questions. e.g. For "Bus Wash", further determine "Dropdown options: School bus, Party bus, Church bus" Goal: Generate a report that shows the Customer Name, Customer Project (I can do this part so far), and [a list of information based upon the Project Elements] <-- this is the part that I am struggling with how to do. Especially with how to structure the follow-up questions. For example: If a Project Element is "Bus: School bus", it would display a specific set of information on the report about school busses.
Your concept of "checkboxes to add them to the report" is likely not practical for 2 reasons: if this is a multi-user database, users will conflict with each other editing the check field since the checks will change for each project, there will not be history Each project can have multiple elements and each element can belong to multiple projects. This is a many-to-many relationship. This requires a third 'junction' table that associates projects with elements. This junction table can possibly have fields for the additional attributes describing the elements but more likely will need another table. Possibly another 'junction' table to associate selected element with selected attributes. So the ID of the ProjectElement junction table will be referenced as a foreign key in SelectedAttributes table. Each record will be an attribute associated with the ProjectElement record. This means you will need a lookup table of all possible combinations of element/attribute. Then a cascading (dependent) combobox can be used to limit dropdown list to only attributes applicable to selected element. Requires VBA. Might want to use form/subform/subsubform arrangement - forms can go 7 deep.
How to combine two fields in Form to one field from Microsoft Access?
Report building from selection in datasheet
Multiple arguments IsNull function MS Access VBA
how to pass parameters to ExportWithFormatting using vbscript
Access 2010 cascading combo boxes runtime error 424
Access Month Calendar View
Shapefile to MDB with custom field structure [duplicate]
Query JET 4 database with SSIS
Microsoft Access 2010: Query Criteria moving
Is there a way to create an Access database from a Visio database model?
Access: insert multiselect box values into database
ms access extra table indexes
Recordsource vs Recordset for Unbound Forms
Access Database Remote Connection
How to programmatically convert Access 1997 .mdb to Access 2007 .accdb
Microsoft Access Duplicate Output Destination workaround