Hi there,
I'm working on my A2 IT Access project atm, and my aim is to produce a fully functional db for use by a golf course, incorporating membership information and tee-time reservation system.
I've got the membership side pretty much sorted, so now I need to start work on the reservation system.
But where to start?
Basically, the user needs to be able to view slot availablity on a specific day, and make/change/delete bookings quickly and easily. The booking also needs to contain the party size. The bookings themselves should relate back to the specific member that made it via the MemberID field.
The user should be able to make bookings upto 6months in the future.
Block bookings should also be possible, so that the admin can block an entire day out for a tournament therefore preventing member bookings.
The first available and last available slots also need to be editable by the system admin to take into account time of year, light conditions etc.
Right, so i know there's quite a lot there, and i'm sure i'll come up with more features that would make it better.
But as it stands, that's something to get me started.
I'm not asking for someone to do the project, just to point me in the right direction as to suitable table structure, how to "make" the slots, how to store the bookings in the table, etc.
So, any input and ideas are greatly appreicated.
Cheers
Gavin W
I'm working on my A2 IT Access project atm, and my aim is to produce a fully functional db for use by a golf course, incorporating membership information and tee-time reservation system.
I've got the membership side pretty much sorted, so now I need to start work on the reservation system.
But where to start?
Basically, the user needs to be able to view slot availablity on a specific day, and make/change/delete bookings quickly and easily. The booking also needs to contain the party size. The bookings themselves should relate back to the specific member that made it via the MemberID field.
The user should be able to make bookings upto 6months in the future.
Block bookings should also be possible, so that the admin can block an entire day out for a tournament therefore preventing member bookings.
The first available and last available slots also need to be editable by the system admin to take into account time of year, light conditions etc.
Right, so i know there's quite a lot there, and i'm sure i'll come up with more features that would make it better.
But as it stands, that's something to get me started.
I'm not asking for someone to do the project, just to point me in the right direction as to suitable table structure, how to "make" the slots, how to store the bookings in the table, etc.
So, any input and ideas are greatly appreicated.
Cheers
Gavin W