There are many many things to consider and it depends what you want to do.
For instance you could have a Recording table and a RecordingRelease table
to deal with multiple formats LP, MC, CD, SACD, MP3, DVD-AUDIO the
RecordingRelease would contain data specific to the format and the Recording
would contain data about the recording whatever format it was released in.
It would probably be crazy to have a table for CD and one for Musicassette
and one for......
As to Artists and Recording/RecordingRelease you will need to resolve the
Many to Many relationship as per the usual approach with a table with a 1 to
Many relationship from Artist and a 1 to Many from
Recording/RecordingRelease.
It depends entirely upon the use you wish to put the database to.
A system designed for Sony may differ to one designed for a private
collection.
--
Slainte
Craig Alexander Morrison
Crawbridge Data (Scotland) Limited
Small Business Solutions Provider
"haha" <pr**************@gmail.comwrote in message
news:11**********************@m79g2000cwm.googlegr oups.com...
>I was thinking of making a music database i've created tables but I
cannot make a good relationship out of those tables... here are the
tables I created in access:
CD(cdno,created on)
Cassette(label, cassette no) <has artist(artistno,cdno,cassette
no, artist) <has album(albno,artistno,albumname) <has>
artist(.....)
here is the problem ,
one artist can have many album, and one album can have many artist...
how can I show this relation in access...
