View Single Post
  #3  
Old April 28th, 2004, 05:57 PM
Aaron
external usenet poster
 
Posts: n/a
Default Will my table design cause future problems

I added some key information, hopefully this along with
other descriptions helps. thanks.
-----Original Message-----
Aaron, you will get nowhere with this question until you

identify what is
the "primary key" of each table, and state exactly what

thing or event is
identified by each row in the table.

For example:

tblClient - one row for each client known to the system.
ClientID (PK)
Forname
Surname
etc.

This might help:
http://support.microsoft.com/support...cles/Q100139.A

SP

HTH,
TC
(off for the day)


"Aaron" wrote in

message
...
Access/VBA newbie here and I have the following

situation:
A research facility mixes elements(LotID), processes

them,
evaluates the end product and then uses it in a part

which
will also get tested.
The table structures I have so far:
tblComposition (Lot# can be made up of 1-? elements)
LotID (FK to tblManufacturing)
Element (chemical or metal)
ElementRatio (amount)

tblManufacturing
LotID (PK)
ProcessEquip
RunDate
%Source

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

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

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.



.