We're using a product that uses Ingres II for its database. I'm accessing the
data with ADO.net via the Ingres II ODBC driver V2.8

There are cases where Ingres II's query test tool reports particular MONEY
values as 5.2 (which is correct), but on some records I get 5.19 in my
DataTable instead.
If I got 5.199999999 I'd understand and be able to distinguish that from
5.19000000

I expect the test tool is doing some rounding, but shouldn't the ODBC driver
do that as well?

Any ideas how I can work around this?

(I've also asked CA and the third-party vendor. But if it's an ADO.net
problem this seems the right place to ask.)

<retorical>
When will people stop using floating point for money?
</retorical>

Modifiying a dataview while enumeration it (1.x->2.0 broke)
Saving to a DateTime field in Sql Server 2000 using ADO.Net
Iterating through selects - what is the best approach?
Sharing connection between threads
multithreaded grid-binding problems