Sounds typical of my luck that it's only happening to me! Thanks for helping anyway!
On your other point, if I use it to filter out records (from the 73 total) where the job number contains 'R' (which for the sake of this current dataset would be 3 records), I can't then use the total number of sites as the goal number, as that would also be 3.
I want to display 3 out of 73 on the gauge. Pre-filtering would show 3 out of 3. Does that make sense?
Is there a way of printing out on screen, step-by-step how its calculating to 21,000 something, so I can find the root cause?
I understand the issue with the filter. Below is what I did. Under what does this gauge measure, R Jobs is the count from the query. I selected averaged as the summary since every record in the table will have the same count.
I then set the Gauge limits to the number of records in the table.
This shows 2 of 36 have R in the job code.
As far as troubleshooting, can you put the calculated field and the job number field in a table report next to each other and see what the results are? If the query is on the table with the job number, each record should have the same count. I would review the formula results for each record to see if that has the expected value and go from there.
