It's impossible to say, because you haven't given any Relationships between
the tables. For instance, is it true that:
Each League is composed of One or More Clubs
AND
Each Club belongs to One and Only One League
This will necessitate a different design than one in which a Club can belong
to many Leagues. This information is as important as the table/field
information and you have to have it for every relationship. In essence,
you're asking for a critique without explaining the business rules.
You might want to take a look at the Tutorials Section of my website:
http://www.rogersaccesslibrary.com/TutorialsDesign.html
On it I have several step-by-step tutorials based on the principles in
"Database Design for Mere Mortals" by Michael Hernandez (you should get the
book too), that should make this process easier.
You might also find a pre-built data model here:
http://www.databaseanswers.org/data_models/index.htm

Signature
--Roger Carlson
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L
> I know that the DB design is one of the most important steps in creating a
> project, that is why I am asking for your help. I am novice at using Access,
[quoted text clipped - 85 lines]
> Jeff
> Hd87glide@hotmail.com
HD87glide - 19 Jul 2005 20:01 GMT
Roger, Thank you for your reply. As for the design, there is only one club,
but multiple teams, multiple competitors. There can be multiple teams per
league, but one competitor can only be assigned to one team during one
league. The club table is used more as a control record to show which is the
current league. From here, the queries will find all of the information from
that league.
Thank you for the references, I will be looking into them next.
Jeff
> It's impossible to say, because you haven't given any Relationships between
> the tables. For instance, is it true that:
[quoted text clipped - 115 lines]
> > Jeff
> > Hd87glide@hotmail.com