Scaling of decimal value resulted in data truncation

Michael Noto

unread,

Feb 12, 2002, 8:28:10 PM2/12/02

to

Hi Michael,

My name is Michael Noto. Thank you for using the Microsoft
Access Newsgroups. I searched on the error "Scaling of decimal value
resulted in data truncation" and found Access 2000 cases from 1999 through
2000 and only a couple after the year 2000. it appears that the newer
versions of MDAC may not have this error. If you are using the Microsoft
oracle driver, you may try downloading a newer version of MDAC from the web
site below. If you are using the oracle driver, check with oracle for an
updated driver.

MDAC
http://microsoft.com/data

I hope this helps! If you have additional questions on this topic, please
reply to this posting.

This posting is provided 'AS IS' with no warranties, and confers no rights.

Need quick answers to questions like these? The Microsoft Knowledge Base
provides a wealth of information that you can use to troubleshoot a problem
or answer a question! It's located at
http://support.microsoft.com/support/c.asp

Regards,
Michael Noto
Microsoft Support

Michael Ralph

unread,

Feb 13, 2002, 10:24:47 AM2/13/02

to

Thanks for that. Unfortunately, the 3rd party who wrote
the software & ODBC driver haven't released a more recent
version so, although I do have the most recent MS drivers,
they don't help.

However, as Excel isn't as fussy about what it imports,
I've been able to view the data that it's failing on. In
addition, by opening the table via Access although it
causes the error message, it was retrieving some records.

I have now discovered that it's failing on a numeric field
that, in the originating data, can contain up to 15 digits
to the right of the decimal point. As Access (2000 & 2002)
- now treat such fields as "decimal" with a scale of 8 -
it's bombing out on those ('97 allowing it as a "double").

Question is - can I force the properties of a linked table
to differ from the underlying data type? In this instance,
I don't actually need that level of accuracy (or even that
particular field!) but can't find a way of getting Access
to ignore it

Michael Noto

unread,

Feb 13, 2002, 11:08:51 AM2/13/02

to

Hi Michael,

I do not know of a way to change the change the way that the
ODBC driver interprets data types. Some of the cases I looked at were
resolved by changing the data type from a number data type to a decimal
value.

Guy Outred

unread,

Mar 8, 2002, 5:42:33 PM3/8/02

to

Here's the solution I found using Access 2000 alone:
Once the link tables to the Oracle database are created, create
another access mdb file and import those same tables into the new
database. This will result in those same linked tables existing in the
new database, but now you should be able to write queries against them
that actually return the decimal values.

I suspect this does tuncate the data if the Oracle values exceed the 8
decimal place limitation of Access, but at least it doesn't bomb
anymore.

I'm a little suprised that this issue, which is pretty common in these
groups had not been resolved by Microsoft. I think the MDAC update was
a red herring.

mike_...@online.microsoft.com (Michael Noto) wrote in message news:<3OkTGjKtBHA.1572@cpmsftngxa07>...