"Decimal fields precision is too small..."

[maw230]

Decimal fields precision is too small to accept the numeric you attempted to add.

That is the error. I've searched the forums, and although im sure there are similar posts i could not find any. Google didn't help too much either.

the query is linked through ODBC to Access 07. I can post the SQL, but it is a little messy do to a lack of aliasing and using Design mode.

ive attached an example of the #Errors that appear in the records when i run it as a select query - which is the only way the query will run.

 

[RuralGuy]

What is the BackEnd system and what is the field type.

 

[maw230]

The back end is IBM AS/400.
I am not sure which field is causing the error as there are 5-6 decimal fields being returned by the query. I tired rounding each one but that didn't work.

 

[RuralGuy]

Are you doing any calculations in the query?

 

[maw230]

Nope there aren't any calculations..

 

[boblarson]

Have you tried using the NZ function just in case Nulls are causing a problem?

 

[RuralGuy]

How about cutting down the selection of fields to see if you can narrow down the culprit?

 

[maw230]

bob,
No, I haven't. Is there a way to apply an 'is not null' to every field in my query and not on an individual level? Nulls may very well be the problem.
Also, I have never worked with an NZ function and do most of my queries in design view.

ruralguy,
yeah this is something that i was saving as a last resort option because the query is so large.

 

[boblarson]

bob,
No, I haven't. Is there a way to apply an 'is not null' to every field in my query and not on an individual level? Nulls may very well be the problem.
Also, I have never worked with an NZ function and do most of my queries in design view.

In design view you would give your field a new name like:

FieldName1:Nz([FieldName],0)

and no, there is no global way to do it. You would need to do this for all fields; sorry.

 

[maw230]

Thanks, Bob i will give it a shot

 

[boblarson]

You should be able to test on a small set of fields to see if it works for them. If it does then you can expand to the others.

 

[maw230]

Thanks guys found the error. It appears the backend table is having some issues.

 

[RuralGuy]

Thanks for posting back.