bobbypig wrote:GOOGLE CALENDER!
It's free, easy, and reliable...
but if you must do things your own way, I suggest php and mysql. Pretty much, you'll want your database to have the following tables (feel free to change the names):
-workers
-classes
-shifts
-assignments
columns:
workers should contain workerID, classID, name
classes should contain classID, className
shifts should contain shiftID, startTime, endTime
assignments should contain assignmentED, date, workerID, shiftID
explanation:
-workers are entered into the system so that they can be attached with assignments.
They have a class only for the site (so that when you make your php web app, only some classes can edit some data)
-classes simply pair numbers with names so that the site can display a user's class.
feel free to delete this table if it makes more sense for php to parse the classID
-Shifts identify the start and end time of a shift. You can enter many sifts with different (and even overlapping) hours so long as each shift has it's own row.
-Assignments pull everything together, allowing workers and shifts to be paired on a specific date.
with this database, you can design just about any php app to edit it (and I also recommend setting up a cron job to erase old shift data)
