Originally Posted by dmprantz
Yes. That is certainly a way to do it, but I would not use team name as the PK, nor would team members be secondary keys of the team entity. They would have their own PK and have a relation between them. My main point in this is that teams are first class citizens and should be treated as such in the database, not as an attribute of a member.
Then I think we are in agreement. I would use a number as the PK for a team and it's name would just be one of the fields. Relationships from team members to team could be one to many.
12ft competition trailer
Jambo 48 "Bo Diddley"
heavily modified SnP "Chickenator"
[COLOR=Red]Red[COLOR=Black] and [COLOR=Blue]Blue[COLOR=Black] Super fast [/COLOR][/COLOR]Thermapens[/COLOR][/COLOR]