Query result wrong when field is 0

[ebs17]

Note for readable queries: Fields in calculated expressions should also be qualified, i.e. the table name or alias should be placed in front of them so that you can immediately understand which table a field comes from.
...
Nz(??.[PASSAGE# ], 0) AS [COURSE PASSAGE#],
...

@The_Doc_Man already gave this reference, which often remains unread and misunderstood.
This is a point where you can be smarter than the QBE.

 

[cheekybuddha]

Note for readable queries: Fields in calculated expressions should also be qualified

Absolutely.

But, since we don't know from which tables those fields come, it's a bit difficult.

This is the fault of Access crappy query builder, but at least we know that the fields' names should be unique to a single table.

 

[CJ_London]

This is a point where you can be smarter than the QBE.

If it was built in the QBE then table names would be included

 

[cheekybuddha]

If it was built in the QBE then table names would be included

... but not shown when switched to SQL view and copied and pasted here!

 

[ebs17]

Newbies and many advanced users believe that it is good and right to find out what can be found as an SQL statement by clicking on the possible wizard. With this belief, one accept the result as it is, and it looks as shown - very often.
If one don't look at the SQL statement, it doesn't matter.

 

[topdesk123]

We don't need to see the code in the original post, we need to see the code as it is now - i.e. with your use of the nz function

Using the # sign could be throwing it off. Here's another formula you can try:
IIf([PASSAGE#] <= 0 Or [PASSAGE#] < 5 Or [FAILURE#- ESSA] > 1, "No", "Yes")