R
RichardGarfield via AccessMonster.com
Hi
I am designing a classical music database and am a bit stuck on how to manage
the movements of a work.
I have a table Work (primary key WorkID and linked to Artist, Composer etc)
which can have numerous individual movements, each of which has a duration. I
want to avoid the Work table having a load of fields like Movemnt1, Movemnt 2
etc, and Duration1, Duration2, etc.
How can I link to a Movement table for instance, where I do not have to
predefine the maximum number of possible movements as fields - a work might
have 20 or more movements?
I would really appreciate some expert advice.
Thanks
Richard
I am designing a classical music database and am a bit stuck on how to manage
the movements of a work.
I have a table Work (primary key WorkID and linked to Artist, Composer etc)
which can have numerous individual movements, each of which has a duration. I
want to avoid the Work table having a load of fields like Movemnt1, Movemnt 2
etc, and Duration1, Duration2, etc.
How can I link to a Movement table for instance, where I do not have to
predefine the maximum number of possible movements as fields - a work might
have 20 or more movements?
I would really appreciate some expert advice.
Thanks
Richard