Hi LarryE, The fixture list is a list of which teams plays which for the entire season. The match is the physical game being played on that particular fixture date.Doing a little more research, does each "Fixture" consist of a certain number of "games" or "matches" or "legs"? Does each player play an opponent in a "game" or a "match" or a "leg"? And how does scoring work? These are all things that need to be addressed as well. As you can see, this could get complicated. I know little of this subject, I was just going on what you have told us. I think you need to really think about "Fixtures", "games", matches" and "legs" and what the hierarcy is. Only then, can you begin to develop a real model for tracking these things. ACCESS is very good at tracking stuff, but you better get the tables and realationships correct from the beginning or you will have nothing but problems.
I would take pencil and paper and draw a hierarcy picture of all the parts you need including Seasons, Divisions, Teams, Players, Fixtures, Games, Matches and Legs. Then you can build your model in ACCESS from there. It this point, we are just guessing.
The match comprises 3 games (legs) where the whole team participates and results in a number of wins for the home or away team, namely : 3-0, or 2-1, or 1-2, or 0-3 so 2 text boxes allowing 0,1,2,3 and a rule allowing the the total of the pair to always add up to 3.
Then, 3 doubles games comprise
home players 1 and 2 against away players 1 and 2
home players 3 and 4 against away players 3 and 4
home players 5 and 6 against away players 5 and 6
Then 6 individual games
home player 1 against away player 1...........>> home player 6 against away player 6
I'm considering having separate tables for each of the type of game against the fixture , team and players.
An old scorecard attached to make my rambling a little clearer..
Continuing thanks.