Table Design Questions

[DaveMac]

I have a design question. I am trying to design a set of tables and am running into some concept problems. I understand the concept of splitting tables into their relevant data sets and linking them to partner tables. Not having one big flat table with 48 fields breaking it into several related tables. Unfortunately I am now stuck. Here is what I have:

Tbl_Production_Reporting
Prod_ID
Shift
Date
Supervisor

Tbl_Prod_Rpt_Pre_Prod
Prod_ID_Pre_Prod
Prod_ID
Demand_Small_Parts
Demand_Med_Parts
Demand_large_Parts

Tbl_Prod_Rpt_Prod_Area
Prod_ID_Pro_Area
Prod_ID
Small_Parts_Made
Med_Parts_Made
Large_Parts_Made


Tbl_Prod_Rpt_Post_Prod
Prod_ID_ Post_Prod
Prod_ID
Small_Parts_QCed
Med_Parts_ QCed
Large_Parts_ QCed

Tbl_Prod_Rpt_Shipping
Prod_ID_Shipping
Prod_ID
Small_Parts_Shipped
Med_Parts_Shipped
Large_Parts_Shipped


My Questions are
1-Is there a fundamental flaw in this table layout
2 – As you can see Prod_ID is the link for all the detail tables to relate to the actual shift table. The problem is when I create a query to link them all then make a form from the query it does not work. After I put 3 tables together the query stops allowing data to be entered.??????????

 

[fneily]

See:
Harnessing the Power of Updatable Queries

http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dnaraccess/html/msdn_harness.asp

 

[barny2006]

i think small_parts, medium_parts and large_parts a quantity field? a yes/no field? or what?

 

[DaveMac]

yes Qty fields.

Reading the MS paper looks like everything should work but I am still checking to make sure the one-many parts are correct however I did that one time already.

My thoughts were is there some limit to how many different tables can be joined in one qry before it is no longer updateable