"Aaron" wrote in message
...

(snipped)

A research facility mixes elements(LotID), processes them,
evaluates the end product and then uses it in a part which
will also get tested.

So:
- each part has one (or several?) tests;
- each part comprises several end products;
- each end product comprises several elements.
Correct?


tblComposition (Lot# can be made up of 1-? elements)
LotID (FK to tblManufacturing)
Element (chemical or metal)
ElementRatio (amount)

What is the primary key of that table? What does one row in that table,
represent?



tblManufacturing
LotID (PK)
ProcessEquip
RunDate
%Source

What does one row in that table, represent?


tblEvaluation (characterization of LotID's after mfg)
LotID (FK to tblManufacturing,no duplicates)
ParticleSize
ECValue
FinalMAss

What is the primary key of that table? What does one row in that table,
represent? (I don't understand: "characterization of LotID's after
manufacturing". You need to describe the table in terms of the entitites you
have mentioned so far: parts, tests, elements, end products, etc.)


tblParts
Part# (PK)
LotID (FK to tblManufacturing)
Account
Performance (test data of Part#)

Aaron, that is the only table that is clearly described so far. Each row in
that table represents a single, unique Part. Each part is identified by a
unique Part#. Part# is the primary key of that table. We need the same level
of understanding of your other tables, before we can comment.

HTH,
TC



One of the key deliverables from this database is to
provide Evaluation data and Part listings for every
combination of Elements and %Source information. i.e;
LOT#AALL12 had a 10%Source and was made up of Al,Si,Cu at
a ratio of 60,20,20 and was used in PART#1234,PART#5678,etc
If I continue down this path I will need to concatenate
the records in the tblComposition and I don't know how big
a problem that will be. I also don't know what other
problems I am not considering. Please advise. Thanks.