Vincent it right. I'd really suggest that you search the net for some database design tutorials. I can't think of any off the top of my head, but I've read a few and they are very helpful if you don't know much about database design.
You could even break vincents idea down into two more tables if you wanted, that being a table of available dates and a link table. So you'd have 180 rows in that table 1 for each day that someone could play golf, then youd link each of those days to a tee time, and finally you'd link that link to each of the players so that you could see who was golfing at each tee time.
This would give you 180 rows in 1 table, 120 rows in table 2, your date/time link table would have 180120(21600) rows, and then you'd have your players table and your players link table, since your players table is dynamic I can't calculate the number of rows you'll have, but your link table could have a maximum of 21600(players*4) rows, that is if you have 4 players per tee time.
