Reservation/Tee Time Service

[Wario]

Seems you are asking what is the best way to structure your reservations database table?

The way I would structure it is like this: (the way I think you are describing it)

Date .................................Time ................................Player 1.......................Player 2................................Player 3.......................................... Player 4
17th March 2012.............. 07:00
17th March 2012.............. 07:10
17th March 2012.............. 07:20
..................
etc.,
...................
18th March 2012.............. 07:00
18th March 2012.............. 07:10
18th March 2012..............07:20


The fields Date and Time are date/time DataType
The fields Player 1 to Player 4 are text fields for the name of the player.
The field can be left blank for a free slop of filled with some the text such as "Available"

I think your query is that this structure is flat and the date repeats quite often which goes against one of the principles of good database design (think it is called "redundency?" maybe "repetition").

Database design is always a compromise and in this case I think the above is the best way to do it.

There are about 65 tee times a day so you will end up with a table with 23,000 records for a full year which is tiny.