many to many relationships

[lowrider]

I've read a bit about junction tables, but I'm still not
sure I have it right. Is it necessary for there to be a
third field aside from the PK from the other two tables?
I've read that the third field needs to be common to
both, and I'm not sure how to incorporate that into my
situation. It is meant to keep track of fixed software
bugs that have been entered (scripted) into an automated
re-Testing machine. One script can test many modules,
(IE Tax and Service Charge) one module can be tested by
many scripts. Here's where I am at:

TblScript

Script ID * - autoNum
Bug # - Num
Description of initial bug - Text
Result of test - Text
implemented -(y/n)
Tester Name - Text

TblModule
Module ID * - AutoNum
Module Name - Text

TblScriptModule
Script ID *
Module ID *

Also, once I've correctly established the relationships,
can I use a combination of these tables in an
input/update form?

 

[Douglas J. Steele]

It's sufficient to have only the PKs from the other two tables. There's no
requirement to have any additional fields, unless they make sense.