If you read up on aggregate functions, you'll find that if you refer to a field from a related table, what you report is what is the expected result.
But why do you have three different game scores in the same record?
The answer to your issue would seem to be to put those scores into separate records rather than three scores in the same record so if we know why you have used three score fields in the same record, we can suggest an alternative.
Well, there are three scores per game because there are always three game scores per game (i.e. the definition of a game is 3 scores).
I guess I could create a separate table to hold the scores, but that would tend to make a lot of other areas more complicated.
I could take a look at it, but may end of dropping the idea. Adding the stddev was just a cute statistic to provide, but it sounds like it may end up being way more trouble than it's worth.
to me, a separate record for each score makes for a better database design in the first place. The Score records can all link to a common game record.
Yeah, I agree. It was just easier at the time.
Thanks for the help!