Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Current Record

Discussion in 'Information Technology' started by michael_parry2005@hotmail.co.uk, Jul 28, 2006.

Tags:
  1. michael_parry2005@hotmail.co.uk

    Guest

    Hi

    I am creating a music database and could have more than one album per
    artist, is there anyway to count the number of times an artists name
    appears in on of the table coloum. eg. record 1 = abba then record 223
    would also contain abba, so when the user looks at the database it tell
    them on the first abba field that there is another.

    thanks for your help
     
  2. Loading...


  3. Joseph Meehan

    Joseph Meehan
    Expand Collapse
    Guest

    michael_parry2005@hotmail.co.uk wrote:
    > Hi
    >
    > I am creating a music database and could have more than one album per
    > artist, is there anyway to count the number of times an artists name
    > appears in on of the table coloum. eg. record 1 = abba then record 223
    > would also contain abba, so when the user looks at the database it
    > tell them on the first abba field that there is another.
    >
    > thanks for your help


    I might add you might also want to know how many tracks an artiest has
    and how many artist are on a given album.

    The artist name should only occur once in a table and not the the table
    listing the albums.

    You should have an artist table. If you are putting the artist name on
    each track or album in a table you have a non-normalized table. That is
    like using Access as if it were a spreadsheet.

    I would expect a music database to have several tables.

    Album: (this would normally be each record, tape etc.) You would have
    one record for each discrete piece of media.

    Track: You would have from one to many tracks on each album. Normally
    each track would be a separate song. This table would list all the songs
    you have.

    Artist: This would list each artist

    Group: this would list each group of artist. Considering members of a
    group change from time to time, you might want to have different subgroups
    based on who was in the group at the time.

    A group would be related to one or more artist and also to one or more
    tracks.

    Artist would be related to one or more tracks.

    How detailed you may want to go would be up to you. You could easily
    list each artist for each track.

    Once you have the data structure set up properly, getting the answer to
    your question is a lot easier.

    Since this is a rather common use for a database, you can do a little
    searching for "Access music templates" and likely find many examples and get
    ideas from them.

    --
    Joseph Meehan

    Dia duit
     
  4. michael_parry2005@hotmail.co.uk

    Guest

    Thanks very much for that reply its been a great help

    I not puting a better structure to the database
     
  5. michael_parry2005@hotmail.co.uk

    Guest

    Thanks very much for that reply its been a great help

    I now puting a better structure to the database
     

Share This Page