off course, but this is a different subject, means a finished, not changing time sheet is to store. in that case I would prefere to use a single record for each sheet holding an id, possibly a date and then a medium text holding a simple xml notation of the sheet. the benetit of that concept is again that the timesheet can have unlimited start stop times. here again is the final rendering of that xml data responsible for the presentation. however the input AND output application would be a bit more complicated. "Ben Dunlap" <bdunlap@xxxxxxxxxxxxxxxxxx> wrote in message news:91.81.14714.34FF97A4@xxxxxxxxxxxxxxx > > 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 > > I agree (unless the app just doesn't have access to the start/stop data). > > Ben -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
