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.
Access 2016 Processes not being killed during Automation but same works for Access 2013/10/07
Unable to use Multivalue field in an exsting Access form
Insert value from textbox into 2 different table ms-access
Access 2013 Expression Builder not displaying
Missing ACCDB database drivers
MS Access Form button that allows user to browse/choose file, then imports file to a table
Can codesmith generator work with MS Access provider?
Access file unable to run in x64
Form.Seltop not selecting top most record
I have an ADO recordset, now I want to create a table from it but not at its connection location. How?
weighted average caluculation in access table
inputting info from one text box to another with command button
Sending attachments using access vba
Removing certain strings in an Access 2010 query
MS Access - Hide Columns on Subform
How to fix in oracle sql developer server new connection acces tab missing?