Weighted Average Returning 0

[morechocolate]

I have seen the problem where weighted averages have returned as blank or zero when they should not. In that instance I had our IT group apply the patch to my machine. I do not seem to be having any further problems, however, another person on another floor was having the problem with a report and we had the IT group (a different person) apply the patch and the user was getting the same results. BTW, when I run the report the user is having problems with, I am getting values for the weighted average.

Anyone have any idea why this may be happening? Could the patch have been applied to the wrong location?

We are running version 8.5 btw.

Thanks for your help.

mc

 

[morechocolate]

I had the user run a different report that I know uses several weighted averages and they are not having a problem.

Therefore, I started breaking down the other report where they were having a problem. I was able to determine that the weighted average is weighted against a formula that contains a field from the database and a formula. The formula is called prin and it used a field called prin_acq + @noncash. The result of that formula is used for the weighting.

Does anyone have any idea why it is on my maching I get a value for the weighted average, but the user is seeing a blank or a zero?

Thanks again

 

[morechocolate]

I wish the search was not down right now.

Anyway, I went up to the users desk and when they try to run the problem report, the datasource dialog box appears (File DSN and Machine). Frankly, this should not happen. Therefore, the user does not have the same ODBC set up that I have. At that users desk, when I changed the datasource to the one I am using for the report, the report results are fine.

I had another user run the same report and they do not get the datasource dialog box. In addition, they get values for the weighted average. Why would the ODBC setting or database have anything to do with this?

Thanks so much.

mc

 

[morechocolate]

Problem solved. The @noncash listed above was the problem. This formula tests one of the parameters and the user was not selecting the parameter. As soon as the user selected the parameter, the problem went away.