common tasks table to be referred in other tables

[Vector]

Hi,
I have a common tasks table m-t-m:
tblPart: PartID, PartNumber, PartDescription
tblTest: TestID, TestNumber, TestTask, TestMinReq, TestMaxReq
tblPartTest: PTID, PartIDFK, TestIDFK

These tables have pre-defined part numbers, test tasks, requirements. e.g.
PartNumber: 111456, 111234, 23156A
Tasks: Measure resistance, Measure Inductance, Workmanship-Check (Y/N)

Now I have a part number being built and tested. Operator needs to create a new record for the part being built with a host of sub-records associated with that part and place actual value measured.

tblTransaction: TransID, PartID, Operator, Date
tblMeasurement: MeasureID, TestID
tblTransacMeasure: TransID, MeasureID, ActualMeasurement

Question1: Is the above logic correct?
Question2: How do I create a form with this setup for the operator to pick a part number from dropdown and see all the tasks and where he can enter actual readings across from each task.

 

[Ranman256]

I use a list box, user dbl-clicks the items, they are added to the subform via append query.
like:

 

[Vector]

Doesn't the append replicates data?
I am questioning
1- The logic of tblTransaction, tblMeasurement, tblTransacMeasure.
2- Getting the right IDs appended and use the IDs to pull the tasks and requirements, and then enter actual measurements.

Please help!

 

[Pat Hartman]

Is the above logic correct?

I don't think so. I would add a type code to the part record and rather than m-m between tests and parts at this level, you would link tests to type codes. Then when a part is created, you would copy the necessary tests by matching on type code and append the tests to the PartTestResults table.