Can't see any of your 5 query calculated fields, but it would seem obvious that one of them results in a divisor of zero in at least one record. That's all it would take.
If one of those divisors is a field where 0 is the default value (in table design) then perhaps you have one record with a 0. Or you might be using Nz and substituting 0 when there is a null value.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
All the others run fine....its this last one thats hanging me up...Can't see any of your 5 query calculated fields, but it would seem obvious that one of them results in a divisor of zero in at least one record. That's all it would take.
If one of those divisors is a field where 0 is the default value (in table design) then perhaps you have one record with a 0. Or you might be using Nz and substituting 0 when there is a null value.
Quick question.....in that naodd field there are numbers like...... 0.2 - 0.6- 0.8 ..............is that a possible error?
If naodd = -1, then the divisor naodd +1 would be zero.
Also, if just one xWIN is not greater than zero, the IIF results in 0 for xWIN. I would think that you'll then have /Count([xWIN])*100 being /Count(0)*100 which would be division by zero. I'd copy the query, remove a field and test. Rinse and repeat until issue goes away. Then the issue is with the last field removed, or with a field which that field uses in a calculation. Once that is known I'd also look at the data pertaining to the field(s) involved in the calculation and look for data that would cause division by zero error. Alternatively, OP could post a zipped db copy here for analysis. The pictures aren't going to help much.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
Good you got it running right and thanks for the star!