Database Design - Monthly Forecasts

  • Thread starter Thread starter dvlander
  • Start date Start date
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
 
John

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

Jeff B.
 
Back
Top