The symptom as reported suggests that the field displaying the value is either defined as requiring only one decimal place or just maybe the displayed width is not the full width of the field somehow but that would seem a bit strange since I would have though it would drop most significant rather than least significant digits (but I don't claim recent exposure to that sort of problem so could be wrong there.)
Is this an ODBC connection to a table or view undertaken for the first time or is there an existing model being applied?
If there is an existing model then that would need to be checked to ascertain the definitions for the field in question (and maybe the other fields as well?)
If there is no model involved at the point that the problem becomes visible it may be necessary to look at the data definitions behind the ODBC connection or the way in which import analysis process is interpreting the data it is seeing.
Exactly what you need to do to investigate there may depend on what the data source is and how it is provided with an ODBC connection.
I hope this helps in some way.