<div>
instead of the listbox, it is better to use a subform bound to the options table, with a combo box with all the options as the rowsource with the master/child link fields set to the Project id
</div>


instead of the listbox, it is better to use a subform bound to the options table, with a combo box with all the options as the rowsource with the master/child link fields set to the Project id

Listboxes.PNG

<div>
<div class="content wysiwyg-content">
I'm looking for advice on how to approach a project database. &nbsp;I'd have a project table and a project details table. &nbsp;But I would also have a &quot;project options&quot; table. &nbsp;This project options table would show all possible choices a user could make for entering into the project details table. &nbsp;I think I see the project options as a multi-select list box on a form. &nbsp;If the user selected for example 25 of the options I would want those options to populate the project details table somehow. &nbsp;But I don't know how to do this.<br />
<br />
Am I even on the right track?<br />
<br />
Looking for advice.
</div>
</div>


I'm looking for advice on how to approach a project database.  I'd have a project table and a project details table.  But I would also have a "project options" table.  This project options table would show all possible choices a user could make for entering into the project details table.  I think I see the project options as a multi-select list box on a form.  If the user selected for example 25 of the options I would want those options to populate the project details table somehow.  But I don't know how to do this.

Am I even on the right track?

Looking for advice.

Looking for advice on how to develop a project database

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.