View Single Post
  #2  
Old April 28th, 2004, 06:58 AM
TC
external usenet poster
 
Posts: n/a
Default Will my table design cause future problems

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...es/Q100139.ASP

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 (created this way because a Lot# can be
made up of 1-? elements)
LotID
Element
ElementRatio

tblProcessing
LOtID
ProcessEquip
RunDate
%Source

tblEvaluation
LotID
ParticleSize
ECValue
FinalMAss

tblParts
Part#
LotID
Account
Performance

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.