Cliff Jones (8/5/2011)
I thought this question was about using approximate data types so got it right for the wrong reason.
I would hope that most viewers of this understand that the FLOAT datatype is generally not a good idea for monetary values, but let's say it to be sure.
I would hope that most people realise that in applications where monetary values range from 0.01 units to 90071992547409.92 units (something over nine hundred million million units), and no greater accuracy than two places after the point is needed, float (which is a synonym for float(53)) is usually far more storage efficient and usually far mor eperformance efficient than any decimal or money type, and no less accurate. Let's hope people also realise that that covers the vast majority of applications involving monetary values.
But. let's say it, just to be sure that the anti-float myth invented years ago by Cobol advocates is not carried over unchallenged into modern times.