Back to the Data Model
A. The requirement is to design a Database to keep track of Musician's Uniforms
I am creating a database for a band I belong to and would like your opinion on the best approach.
The band has junior and senior members, with additional fields needed for parental contacts and
D.O.B. for the juniors.
Each member will either have their own instrument or borrow one from the band.
Each member will have various items of band uniform ( jackets, sweatshirts, coats etc).
I am not sure if it is best to put ALL members in the same table with a field to sat they are juniors or 2 different tables-
I think one which covers all would be best ( in normalisation terms).
The main area that I am unsure about is how to assign the uniform items to each member- at the moment I have fields -
UniformItem1,UniformItem2 etc which all lookup their data from a Uniform table- is the the best approach?
In database notation this is what I have done at the moment:
tblMembers ( MemberID,Forename, Surname,Address,Town,PostCode,HomeNo,MobileNo,YouthBand,DOB)
tblInstruments ( InstrumentID, Make,Type, SerialNumber)
Have I got the right structure or should I have fields in the BandDetails table for Jacket,
Sweatshirt etc rather than Uniform1- or is another approach better?
Any advice would be great, thanks in advance.
February 19th. 2011