Table for Tee Time Bookings. PLEASE HELP!! URGENT!!

I have an assignment due on tuesday, and im really really really stuck with this last table which i need to create.

The idea ok, is to have a database to store the bookings for tee times from a ASP page and a VB program.

The ASP page is all to do with the members loggin in and accesing there accoutn and to make bookings, where as the VB is for the golf club itslef and its employees.

Now i have 3 different types of bookings, 2 are just general bookings, but the third is a tournament which the golf club adds.

Now i had the idea to have 3 differrent tables for those types of bookings, but i also had the idea to have 1 table which i called TeeTimeSheet, to store all the bookings by ID and time and date which i would then use to display a Datagrid with like a matrix style system to show which bookings were taken and which wernt.

My problem is that i can get a table working for 1 week only, the problem is its with no DATE only the DAY and TIME. Anyone here have an idea as to how i should structure the table? PLEASE HELP if you can afford a little time to type it, i cant explain how important this is.

TeeTimeSheet:

booking(AutoNumber), Time(times from 0600 - 0455), Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday.


The times i autogenerated in excel and pasted them. so basically i have all the times available in the TIME field, and i was going to use the other cells under the days to display that cell wether it was booked or not.

Retrieving the information about the booking i was going to do with a BOOKING ID fromwhich i will gather the information, that BOOKING id will be displayed in the cell at which TIME and DAY it has been booked.


once again PLEASE HELP ME OUT if you can, i cant explain how important this is.

It is really hard to a forumn to help people with home work, espically when they put it off so long. With that said.


You are right to only have One table, three would complicate your already overcomplicated DB design. As far as helping you with the rest of you design, it is hard to do this mainly because there are lot of factors that go into this. I personnaly wouldn't design the TeeTimeSheet the way you are I would do it differently

ID, Date, Time, PartyName, #InParty

I would like that to a Timetable to get valid times, have rules that for any given time, No more then four allowed.

When trying to make a booking on the Web, get party name (booking ID), and group size and requested date, then show any tee times that would allow a party of that size on the date selected and have the choose.

DB Design is based on data need, programming style and needs, and viable relationships.

So as far as giving you DB structure advise, it is hard and would take longer thes Tuesday to help in this forumn enviroment. If you have a specific need ask and we will do what we can to help. Advise for next time, DB's take time and planning to get something that you will be proud of, don't wait so long next time.

S-