Hello and thank you for taking the time to read this.

I am trying to create a database for the Praise team at our Church and I can't decide on the best way to do it.

Basically, I will have a series of events and the musicians and instruments will change for each event. These events will have different mixes of instruments. Each musician could be proficient on more than one instrument also.

Any help is appreciated.

Thanks
Scott

Of course...

Last night, about 2 hours after I posted this, the answer came to me.

Thanks,
Scott

Well, it appears that you have three entities.

Events
Musicians
Instruments

Each Event will be associated with one or more Musicians.
Each Musician will be associated with 0 or more Events.
A many-to-many relationship (using an intersection table) would support this requirement.

Each Musician will be associated with one or more Instruments
Each Instrument will be associated with 0 or more Musicians.
A many-to-many relationship (using an intersection table) would support this requirement.

So, one solution to model your requirements would consist of a table for each of the three entities, plus a table for each of the two many-to-many relationships.