Solved Ambigous outer join in query

[Saphirah]

Hey everyone, i am getting the "ambigous outer join" error after running my query. But i dont understand why. My query design looks like this:

How can i remove this error? If necessary i can also send in the content of the Subquery or provide other informations you need for debugging. Just write me below and i would be happy to provide that.

Thank you in advance

 

[arnelgp]

do you have outer join on qry_transport_ladeorte.

 

[isladogs]

As @arnelgp indicated, the problem will be that an outer join in your 'subquery' is conflicting with that in the query you displayed.
You need to fix the 'flow direction' of the joins.
The screenshot is an extract from my article Query Join Types which you may find worth reading

 

[The_Doc_Man]

It is clear that you have a table and a query being joined in the design you have showed. But what is the structure of qry_Transport_Ladeort ?

 

[Pat Hartman]

FYI, the joins in the query have no bearing on the join between the table and the query. In fact, if you need to use both inner and outer joins, you can usually solve the problem by nesting one of the joins in another query. The technique of using a separate query allows YOU to dictate to the query engine the priority in which the joins should be performed. Think of this technique as using parentheses to control how an expression is evaluated.

As Doc said, look at the query. It is likely that the query itself contains the problem join.

 

[isladogs]

@Pat Hartman
Although with hindsight my post wasn't as clear as intended, I would in general agree with your point which is why I posted that extract.
Indeed the usual advice to avoid ambiguous outer joins is to do a query in two stages - as the Access message makes clear.

Having said that if you do try to join a query with ambiguous joins to another query or table, you will see a screen like this:

Although the same message is shown, the actual query with ambiguous joins is displayed with no fields & cannot be joined to anything else.
After clicking OK, the ambiguous join query is removed from the query editor window
For those reasons, I'm not convinced that the original query is on its own the problem here