Field with multiple entries....?

[norlo]

Hello!



I am working on a project for my Final exam for school. I have to make a database about anything I want. I chose to make a database about my guitar equipment and the different ways it can be set up. I have run into a problem that I cannot figure out to solve, or if it is even possible (I think it is).

So basically I would like the end result to be a database where I can select all the components from guitar to amp and save it in a certain order i refer to as a RIG (it is the table that joins all the other information together). I have all the tables that I think I need built. The problem is when it comes to pedals I would like each to have multiple settings and the ability dynamically add them to the database. (Some setups may have 5 pedals others may have two, etc.)

For example:

RIG 1:
Guitar 1 -> Pedal A(setting a) -> Pedal B(setting B) -> Amp

RIG 2:
Guitar 1 -> Pedal B(setting d) -> Pedal D (setting A) -> Pedal A (setting C) -> Amp

So I need to be able to add however many pedals I need to each rig, maintain thier order and be able to choose settings for each.

YEah a loded question, I'm not looking for you to do this for me. Just give e a kick in the right direction.

Thanks,
Nick

[orange]

Suggestion:
Don't use a field that allows multiple entries.
Do a little searching/investigation of "normalization".

There is a write up on Normalization here.
http://www.rogersaccesslibrary.com/forum/topic238.html

The first 3 topics are an excellent reference.