Reporting with Crystal v.10, off MS-SQL Server data...
This afternoon my boss showed me a report I've heavily modified. An error was evident, where in groups of "facility type" with only one facility, the daily average column in the "facility type" GF row did not agree with the daily average column of the "facility" GF row. If there is only one facility of a given type, the facility type daily average should agree with that of the one facility, of course. There only seemed to be a discrepancy in that scenario.
I tried to recreate the error by running the report myself. The error did not occur. The column averages agreed. I went back to my boss. He ran the report of the same name in the same folder and the error did occur. We tried running the report from Crystal Reports itself and from the application report user panel. In each case, my boss got the error and I did not. Someone had reported the error to him, so it was occurring on a PC in addition to his. I tried to run the report from a machine other than mine and the error did not occur. We all use the same version of Crystal. Très mystérieux.
Can anyone suggest a line of investigation?
Thanks in advance for your reading and thoughts,
Brad Macdonald
This afternoon my boss showed me a report I've heavily modified. An error was evident, where in groups of "facility type" with only one facility, the daily average column in the "facility type" GF row did not agree with the daily average column of the "facility" GF row. If there is only one facility of a given type, the facility type daily average should agree with that of the one facility, of course. There only seemed to be a discrepancy in that scenario.
I tried to recreate the error by running the report myself. The error did not occur. The column averages agreed. I went back to my boss. He ran the report of the same name in the same folder and the error did occur. We tried running the report from Crystal Reports itself and from the application report user panel. In each case, my boss got the error and I did not. Someone had reported the error to him, so it was occurring on a PC in addition to his. I tried to run the report from a machine other than mine and the error did not occur. We all use the same version of Crystal. Très mystérieux.
Can anyone suggest a line of investigation?
Thanks in advance for your reading and thoughts,
Brad Macdonald