Project Description:
I am seeking someone to create a very simple, networked, table view, calendar to be used as a restaurant reservation book. One Single page view in a spreadsheet style format with a few column totals and page up and down buttons. Each Day would have a list of about 50 time slots on each of two pages (Lunch and Dinner). Time slots would be populated with guest information data fields, line by line across the rows.
The purpose of this "table style calendar" is that it needs to be able to be accessed simultaneously by multiple users over my PC Workgroup here in my restaurant. It would be replacing our current simple pencil and paper calendar diary book. It could be hosted as a web page off-site (although off-site access is not needed) or as a program on a local PC server on-site. (currently 5 PC work stations)
Each Calendar Day should have it's own full page table, each day's table accessed by visually paging forward or backward in some way.
Each time slot would need unique limits on the number of guests that could be entered (maybe a drop down box?) to prevent overbooking and control guest flow.
A calendar pop-up would be needed for accessing dates far in advance.
Color coding of fields, times, and days of the week would be required to make the table more visually appealing and simple to use.
This is basically a simple spreadsheet with a relational database. I had considered creating a Google document "in the cloud" but the ability to protect labels and certain fields posed some issues. I had also considered having someone create an Excel spreadsheet but did not want the expense of networked spreadsheet software (MS Office) on all 5 work stations.
I also need the ability to prevent employees from making certain changes and at the same time the ability for managers to override certain values and insert additional time lines as needed.
Also need the ability to print out each individual day's calendar.
No log-in would be required. We need the ability for multiple employees to quickly work from the same front desk terminal without the need to log-in. Users would be required to enter some sort of name, initial or ID# to identify that they filled that time slot line.
Edits and changes could be password protected in 3 or more privilege levels. Admin... Manager... User...
