Thanks, jay.
Well, I did end up with the result I needed by issuing the ROUND (expression, 1) which resulted in 58.00 in the output field. Not sure if that is an appropriate way to handle this.
So, this is not about the incorrect setting of precision and scale in the table?
The original data and application came from Access97 and these fields were set to "Auto" (which I believe automatically determines the output for the calc). Migrating the db tables to SQLServer2005 has caused some confusion as to which is "more" correct, $58.01 (what SQLServer calcs as an output result) or $58.00 (what Access calcs as an output result).
I don't necessarily want to force the output numeric value just because it matches what the old database produced or what the users think it should be, I want it to be accurate. The problem is that .01 difference means a lot when dealing with hundreds of thousands of rows.
Also: the output is a "charge" value, or currency. But the orig db had this as number(auto) field type. Would you reccomend changing this field to Money type?
jfc