questions about tables/relationships

[outrider]

My boss has assigned me the task of constructing what is basically a time tracking database. Employee info will include Employee ID, Name, Work Area, and Supervisor's name. Each day, employees will record the time they spend working on any of 40 different potential tasks for that day. The forty different tasks are split into five main categories, each with eight tasks. The boss wants each employee to be able to go into a form and/or subforms (haven't gotten that far yet!) and be able to record the amount of time they spent working on any given task for that particular day.

So, the tables would need to contain the Employee info mentioned above, the date, the 40 different potential tasks, and the time spent on each task for each day. I can't quite get my arms around how i should set up the tables, particularly where the date would go. Hope i was clear enough describing what I'm looking for. If not, let me know.

Thanks in advance for any suggestions!

 

[gemma-the-husky]

are you used to access etc? this seems like quite a major exercise to me - a bit of a poisoned chalice if you are new to it

 

[outrider]

I am familiar with access. I have never built anything from the ground up though. I set up the tables in a way that made sense to me, but after reading around, I discovered that my tables weren't properly normalized. It would probably work my way, but this database will be the standard for my department, so I want it to be built properly.

 

[Adeptus]

Off the top of my head...

One table for employee details
ID, name, etc

One table for task/category details
(ID?), category, task

One table for "timesheets"
(ID?), employee, date, task, time spent