sorry man, but a good data design keeps only data in a table u can not calculate. in ur case that would be only <date> <start> and <end> time. refernces to user and project/tasks in other tables. ur time sheet is definately a job for a report. that type of design limits u to nothing. a user can start ans stop as many times he wants a day or time range. u can report any number of time bits to any number of project a day or time range Ralph "Shawn McKenzie" <nospam@xxxxxxxxxxxxx> wrote in message news:5E.47.03459.7EAD97A4@xxxxxxxxxxxxxxx > So, obviously not PHP related, but I'm looking for thoughts on the best > way to record time sheets in a DB. A time sheet for hours worked per > day, not like a time clock where you start and stop. > > The two possibilities that I have thought of are (these are simplistic, > of course I'll be storing references to the user, the project code etc.): > > 1. One record for each 7 day week (year, week_num, d1, d2, d3, d4, d5, > d6, d7) where the dX field holds the hours worked > 2. One record for each day (date, hours) > > -- > Thanks! > -Shawn > http://www.spidean.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
