The decimal field's precision is too small to accept the numeric you attempted to add.

M

MyndPhlyp

That subject line is an error message from Access 2000 on a Win2K Pro
workstation when viewing the table data in a linked FoxPro table.

I had been experiencing difficulties filling a column defined as a Decimal,
Precision=16, Scale=5 with the value:

240

Last time I checked, 240 was well within the range. What I did to see if it
was Access was to go into the application that actually uses the FoxPro
database and entered the value through the product's form, and then went
back to Access to see what it looked like.

Found a KB at Microsoft referencing the exact error message:

http://support.microsoft.com/default.aspx?kbid=270704

The problem was first addressed in Jet v4.0 SP6. I already had Jet 4.0 SP8
installed in addition to MDAC v2.8 (and reinstalled anyway).

The KB included a list of DLL versions in Jet v4.0 SP8, so I checked the
system just for grins. The mismatches were:

msexcl40.dll (higher version installed) v4.0.8618.0 versus v4.0.8015.0
msjet40.dll (higher version installed) v4.0.8618.0 versus v4.0.8015.0
msjetoledb40.dll (higher version installed) v4.0.8227.0 versus v4.0.8015.0
msjint40.dll (LOWER version installed) v4.0.6508.0 versus v4.0.8015.0
msjtes40.dll (higher version installed) v4.0.8618.0 versus v4.0.8015.0

Other than that, all the other DLLs matched.

I'm a little concerned about the MSJETOLEDB40.DLL and especially the
MSJINT40.DLL.

I would appreciate it if somebody here with a similar installation checked
the versions of these 2 questionable DLLs and post the results. (They are in
WINNT/SYSTEM32.) Win2K Pro, Access 2000, Jet v4.0 SP8 and MDAC v2.8.

Is there a command line switch for Jet v4.0 SP8 and/or MDAC v2.8 that tells
the installer to force the files into place regardless of version?

Anybody know of other causes for the error message I'm receiving? (I really
gotta fix this!)
 
P

Pieter Wijnen

I'm not happy with the way Decimal work in Access - it does tend to mess up
the data (ie Math) -
(any comments to the contrary will be appreciated)
my suggestion is to use double for fields instead of decimal

Pieter
 
M

MyndPhlyp

Pieter Wijnen said:
I'm not happy with the way Decimal work in Access - it does tend to mess up
the data (ie Math) -
(any comments to the contrary will be appreciated)
my suggestion is to use double for fields instead of decimal

Pieter
Click to expand...

Were I designing the database, that would be one possibility. Unfortunately
the target table is part of a database used by a commercial piece of
software and it is not an option. I have to play the cards dealt to me.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Run-time error 80004005 - HELP! 1
Access - FoxPro: The Decimal field's precision is too small to accept the numeric 0
"The Decimal field's precision is too small to accept the numeric you attempted to add" 1
"The Decimal field's precision is too small to accept the numeric you attempted 0
Linked DB2 Tables and "Decimal field's precision is too small to..." Error 2
Decimal Field's Precision Too Small to accept the numeric you ... 3
Decimal fields's precision is too small to accept the numeric youattempted to add 7
The decimal field's precision is too small--when making query by access 1

Top