I don't follow the design you're thinking about from the post, but here's how I'd approach it:
A table to describe a Team, with a TeamID
A table to describe a Player, one row for each with a PlayerID
An intersection table of PlayerID and TeamID with from/through date ranges, one row for each Player on each Team (better to have a separate table than put the team information on the Player row because it can change over time)
A table to describe the Golf Course, one row for each with an CourseID
A table for each Hole, links to the CourseID, and has various information about that hole (par, length, etc) with a HoleID. Might need these to be date specific if the relevant information changes; so you could have several rows for the same hole at the same course.
A table of Events (league play, tournament, etc) with dates, description and an EventID
An intersection table for a Round played, has date, links to a CourseID and EventID.
An intersection table for each player in the round, each row has RoundID, PlayerID, (handicap?), etc that applies to that player on that round
An intersection table with one row for each RoundID, PlayerID, HoleID. Number of strokes, putts, etc the player had on that hole, in that round.
