League database

I am trying to work out how to structure a database for a league table for a darts league. There are 4 divisions and each team plays 15 other teams on a home and away basis. The winning team is awarded points for each individual game they play, plus 1 extra point if they win the match.

I am struggling to think how to structure this so that I can produce a fixture list and record scores and output a league table on a weekly basis.

If anyone can help I would appreciate it.

This may be beyond me as I am a learner, but I thought I should try to develop something useful for myself, at least.

Thanks

Harlequeen

I am working on the same type of setup, fewer teams smaller, but am building it for the future I hope. Used to use dartman to manage it, but it is cost prohibitive right now so am going to put together an idiot proof (meaning myself) data base using access, but it has been a while since I have done much creating with access.

Well the basics are pretty simple:

tblTeam
teamID - Primary key
teamName
teamManagerName
teamManagerEMail
teamManagerPhone
teamPoints

tblDivision
divisionID - Primary key
divisionName

tblDivisionTeam
div_teamID - Primary key
divisionID - Foreign key to tblDivison
teamID - Foreign key to tblTeam

tblMatches
matchID - Primary key
matchDate
homeTeamID - Foreign key to tblTeam
awayTeamID - Foreign key to tblTeam
*homeTeamPoints
*awayTeamPoints

* You may or may not want these fields based depending on how you want to keep track of the points.

Do you need to keep track of the outcome of the individual games in the DB? If so do you need to keep track of the scores or just who won?

Do you need to keep track of the players for each team?

Apologies for the thread resurrection, but I found this relevant topic while researching for my own league database.

I have some queries on dykebert's helpful starting point:


tblTeam
teamID - Primary key
teamName
teamManagerName
teamManagerEMail
teamManagerPhone
teamPoints

tblDivision
divisionID - Primary key
divisionName

tblDivisionTeam
div_teamID - Primary key
divisionID - Foreign key to tblDivison
teamID - Foreign key to tblTeam


i) I haven't understood the purpose of tblDivisionTeam.
On the basis that one Division has many teams I would have expected 'divisionID - Foreign key to tblDivison' to be in tblTeam.



tblMatches
matchID - Primary key
matchDate
homeTeamID - Foreign key to tblTeam
awayTeamID - Foreign key to tblTeam
*homeTeamPoints
*awayTeamPoints


ii) I note that tblMatches has a limitation in that it only allows 2 teams per match. I will need more flexibility (to cover multiple sports/event types). I'm thinking of splitting the table into two (as below). tblEvents would have a record for each match/event. tblResults would have a record for every team participation. Calculating event winners and league points may be more complicated though. I will want to record scores of individual events and calculate the necessary league points from them.

tblEvents
matchID - Primary key
Date
Venue

tblResults
matchID - foreign key to tblEvents
TeamName - foreign key to tblTeam
TeamScore
TeamLeaguePoints

Any thoughts on this issue would be appreciated.
Thanks, G.