What is the best way to design this? Basically, I want to avoid duplicates - but my question is, is it better to use more tables or have a small number of duplicate entries? Consider the following (sorry I can't space it out or use tabs so I've separated the fields with a slash):
FirstName / LastName / Article / GroupName
Paul / McCartney
Paul / McCartney / and / Wings
/ / / Wings
Mike / McCartney /
Paul / Simon
Diana / Ross
Diana / Ross / and the / Supremes
/ / / The / Supremes
I have separated the Articles for sake of sorting and so I don't have a silly printout of "Supremes (The)".
So, is it better to have one table for each of FirstName LastName and Article GroupName (together) - in order to maintain the integrity of a single "Paul" entry? That way I could use "unique" in the database - but it seems like an excessive amount of tables. Or should I make one database with the above layout and handle duplicates with an "if" "where" there is a match for more than 1 field (ie if Paul McCartney is entered that's a duplicate - but you can still enter Paul Simon.)
I would like the form to display the above 4 fields.