Database Design - Monthly Forecasts

D

dvlander

Suppose I have a table of project assignments. Each of these assignments
will have selected data for the future X number of months such as forecast,
projected utilization, actual utilization. Is it poor design technique to
have separate fields within the project assignment table such as
Jul09Forecast, Jul09ProjUtilization, Aug09Forecast...?

Does it make more sense to create a separate table with monthly fields
(Month, Forecast, ProjUtilization, ActualUtilization) and then link it to the
assignments table?

Thanks, Dale
 
J

Jeff Boyce

John

My wife regularly reminds me that I have fewer words to use each day than
she does...<g>

Jeff B.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top