Access - ODBC - Oracle Integrity?

We have Oracle databases running on a unix machine and we are using MS-Access as a front end to view, modify and add data via ODBC and Oracle's SQL*Net.
Only recently we discovered a bad error in our system. In cases where we have a NUMBER field in an Oracle table and we are putting data in that field through Access. When we put the number 44 in the field the number 46 is stored instead. This happens every time when we put the number 44, except when we use a SQL pass through query. We have not observed/don't know of any other number that behave like that. We tried doing it with update query, recordset in access basic, by exporting data and use datasheet. We also tried Oracle version 6 and 7 and two types of ODBC drivers but same happened. Then we tried to use Visual Basic via ODBC and that worked until we installed Microsoft Jet Database Engine version 2.0 /Visual Basic version 3.0 Compatibility Layer. So it looks like the error is in the Jet Layer 2.0.

I would be glad to hear from people that have tried something similar. We have tried to talk to our "Microsoft Solution Provider" but we haven't got any answer yet.

Thanks in advanced.

Tomas Erlingsson                                      | email:
National Physical Planning Agency                     |   tomas_at_islag.is
Reykjavik - Iceland                                   |   tomase_at_rhi.hi.is