quote:

---

Originally posted by cidr2

HI There,

This is a short one and would like someones opionion

I have to create a table that displays info on how much work employees of certain posisions have incurred within the company on a particular project.

For example, a Project Manager may have incurred 5 days of work at a cost of £100 a day. For a Director, the days and costs may be different.

the table schema with both the days and costs would look like this:

Columns
PK ID
FK ID
Project Stages
Assistant Director (Days)
Assistant Director (Costs)
Portfolio Manager (Days)
Portfolio Manager(Costs)
Project Manager(Days)
Project Manager (Costs)
Performance Auditor(Days)
Performance Auditor (Costs)
Project Officer(Days)
Project Officer(Costs)
Others(Days)
Others(Costs)

---

quote:

---

For each project there would always be 7 rows of info; These rows would seperate the different stages like Fieldwork/research costs incurred. The stages are the Project Stages column

---

quote:

---

My question is, Do you think I should seperate the Costs and Days into two seperate tables or is the above schema acceptable?

---

quote:

---

Originally posted by cidr2

Hi Ahmad and thanks for replying.

I thought about your design idea, and, although is potentially a good idea here, unfortunately due to frontend design issues I've decided to stay with using the Designations as columns and not as rows.

I'm still deciding weather to put the Cost and Days into the same table or make a seperate table.

I don't think it'll make a huge impact whichever way I do it. For reporting I'd use a view anyway to display both columns together, if, in a seperate table.

What's your views, given my decision?

Thanks again:)


Paul

---

quote:

---

Originally posted by cidr2

I understand, and it's a very valid point. I'm assured these columns will not change or expand (Even though it's not always the case where someone says something and it does).

Your design idea, while good, presents issues of design for the frontend (InfoPath) where I can't get round. Unforunately I have to be realistic about the time management and I think it might take too long to design your suggeted idea around the frontend. Hope you understand.

:)

---

quote:

---

Originally posted by cidr2

As far as backend design, your idea to have it as rows and not columns, as far as I'm concerned, is correct.

I'm now working on a way to use the idea and finding a way to have the frontend, consume it as a sort of Pivot table. If that makes sense.

Thanks again:)

---