Many to Many junctions in queries - is there a better way

[Ruegen]

I found that when working with junction tables in queries, when you are trying to get queries across a junction and more than three tables I run into a problem where the data becomes read only.

I found using only the primary keys in the junction as the primary keys for the corresponding tables works fine and the data is still editable in the query however once it starts getting longer it becomes readable. I also get duplicate results sometimes (I'm putting in something wrong obviously).

Is there a better way of handling this when creating queries stretched over more than 3 tables?

I've found that to even show the results I've had to make a query of tables, then put that query into the query and it gets the results I want but then makes that query locked...



The duplicates I have yet to figure out why it is doing that, I suspect I have doubled up an id somewhere..

[Ruegen]

Here is an example, right up until I add another juntion table (to ShowsID that goes to a table called "tblJncPerformers2Shows") everything is editable. It's not read only. However - I add that second junction and it is read only. There are no queries within queries - these are all tables in the image.