Ajax, thx for the thought but, yes, I really want the junction table as Orange surmises. I want the practice of building a classic many to many situation from ground up (in addition to a small utility app for a specialized purpose (which is not a Cartesian cross)). Thank you Orange for that code. I will study it.
As I think about it, the automagical generation of the junction table is a silly idea. As I fill in one of the "one to" tables, how is Access to know which row of the other "one to" table is the one I want paired with it?? Guess maybe I was hoping there was some routine similar to Orange's code built into Access itself, but I guess the answer is "no." If there was, you pros would have found it by now
Thanks everyone for the interesting discussion, -RonL
EDIT - Yeah when I said "the number of junction rows will be the product of the number of rows of each of the "one to" tables", I should have added "MAXIMUM." Sorry Ajax.