RE: Forecast Table

Is it possible to get a little more information, is this your only table?
What is the Primary Key for this table? Also, you shouldn't list your months
like that. There should be a separate table for them that contains MonthID
and Month... in the Month field is where you would put the data January,
February, etc.

--
Carrie


"Mr.LuckyMe" wrote:

I would like to receive your feedback about my table design for forecast. The
forecast is set at product customer level.

What do you think about the following table layout in Access 2003?

ProductID
CustomeID
January
February
...
...
...
November
December
Year

Thanks
.

Relevant Pages

  • EJB3/JPA and versioning
    ... But Page is not an ordinary entity, it's primary key is composite, and ... every page on their lastest version. ... Anyone think it would be possible to implement such layout using JPA? ...
    (comp.lang.java.programmer)
  • RE: Forecast Table
    ... The Primary Key for this table is ProdCustId ... If I understood correct and as my forecast is in Kilograms, ...
    (microsoft.public.access.tablesdbdesign)
  • RE: Forecast Table
    ... Microsoft Access MVP ... In my business case the forecast is kept at monthly level. ... "Duane Hookom" wrote: ... The Primary Key for this table is ProdCustId ...
    (microsoft.public.access.tablesdbdesign)
  • RE: Forecast Table
    ... "Duane Hookom" wrote: ... Microsoft Access MVP ... In my business case the forecast is kept at monthly level. ... The Primary Key for this table is ProdCustId ...
    (microsoft.public.access.tablesdbdesign)
  • RE: Forecast Table
    ... FcstKgID NOT ProdCustID ... The Primary Key for this table is ProdCustId ... If I understood correct and as my forecast is in Kilograms, ...
    (microsoft.public.access.tablesdbdesign)