Different users seeing different numbers *not security*

We discovered that it was, in a manner of speaking, a creds issue.

When I had passed the report along, the new caretakers had their DB connections set to use Windows authentication, not Database. At some point they re-uploaded the report, at which time I guess their connection settings overwrote mine from the old copy. So now, the report was attempting to use Windows authentication with the creds for the PID that does the refreshes?

This for some reason was not crashing the refreshes, but the refreshes were either not occuring or just pulling nothing. The only data available to the report was cached data, so in time the data in a time frame that the users were wanting to see was daily decreasing.

We simpy changed the connection type back to Database, and everything started working again.

I had forgotten that connection settings are local app settings, and not carried with the report. That explains why the data all looked correct to me, even on both copies of the report.