You could have a table of [Matches] with two record link fields, both pointing at a table of [Players].

[Matches] table

In one link field you link all 2-4 players who were in the match. In the other link field only link the one or two players who won. Add another field for points for winning.

[Players] table

Add a Rollup field which sums up all the total of points from the [Matches] table using the link field for games won (as opposed to the one for games played).

Another option would be to have two linked records but set them up a bit differently. Have one linked record for one team and another linked record for the other team. Then use a single select field to say which team won. Conditional roll ups and formula fields could determine the rest as @Kamille_Parks described. This method would preserve the information regarding who was on which team.

Hello @Richard_Benson , not sure if you’ve begun your ‘Tennis Anyone’ solution yet. I always try to use a junction (3rd joining table) when I have a many-to-many relationship between my tables. In your case players] < players_matches] > matches], the ,players_matches] table would be your main working table. There is also a Tournament Bracket template Tournament Bracket Template - Free to Use | Airtable that uses a self-linking table to display your tournament matches in a hierachial graph. They recommend you also install the org chart app to get a more in depth view.

All the Best!

Pablo