Help setting up relationship

[Garret]

Yes it sounds like I was trying to mirror the form and the report too
much, so I'll try not to do that. As for the lookup table you
mentioned before, I don't really know what a lookup table is, but I
found a good article at
http://www.trigonblue.com/AccessLookup.htm
that seems to describe it well enough.

So if I use these tables:

Component

ComponentShipment (a "many" table, related to Component)
ShipmentReceivedDate
Quantity

ComponentShipmentDimension (a "many" table, related to
ComponentShipment)
(ValidComponentDimension lookup) Dimension"#"
DimensionMeasuringTool
PercentPassingToleranceTest

It sounds like I would need a subform on a subform to use
ComponentShipmentDimension?
Does this look correct as far as table setup goes?

 

[Jeff Boyce]

Garret

You left out the "foreign key" fields that tie the "many" tables back to
their parents, and the "lookup" table of valid dimension, which is just
another table that holds something like:
Component
Dimension

Here's one way to check if your table structure is sufficient...

Start asking the questions that need to be answer-able. The "answer" may be
a report, or it may be a screen/form that displays data.

Now take each question and sketch out the query you'd use to get that data
.... which tables hold the individual data elements, how are the tables
joined, which fields do you need, which selection criteria?

If you find that you can't answer one of your questions, what
data/connection is missing?

Use this process to review what table structure is missing.

Regards

Jeff Boyce
Microsoft Office/Access MVP