Decimal Field's Precision Too Small to accept the numeric you ...

[Ken]

I've begun receiving this message over the past few months, but no changes
have been made to the database to account for this.

I am querying a large file for currency fields, summarizing and appending to
a resident table (however, the same thing occurs when I attempt to export to
Excel as well). I sum about 10 fields. The fields in their table are
general number fields, which I convert to currency - Ccur(Sum(Cash)) for
example. I have tried every variation I can think of from changing the
format of the table being appended to all of the numeric options and sizes
(Double, General, Decimal, Currency, etc....), and none have worked - I
receive the same message even when I change the fields from Decimal to
something else, and/or when I change the query to not format as currency,
etc...

Has anyone else encountered this error and have a resolution?

Thanks.

 

[Jerry Whittle]

This "large file" - what is it and how are you reading it? ODBC?

Can you pin down which records cause the problem? Are there nulls?

 

[Ken]

Good questions - I should have known to include the info.

Yes, it is a joined table via ODBC. It contains retail transaction
information. The problem fields are the fields containing tender/amount
values. They are not formatted as currency, but I am trying to convert to
currency as I sum each of these fields over a 1-month period. I have tried
completing the sum without converting to currency, with converting to
currency, and every format option. On a smaller scale (date range about 1
week) I can either make a table or append to a table and sum each field, but
without any formatting. When I attempt to expand the time frame to 1 month
and/or complete currency formatting or any other, that's when I receive the
message. The file appears to be well indexed.

 

[MC_FRx_99]

I am having the Exact same problem.

For me, I'm just trying to bring down the data desired to a local table.

First I did the ODBC link to the source table. Next I copied it and pasted
it as Structure Only to my local Access DB.

Even with presumably having the Exact same table layout, I still get this
error message.

I also tried to increase the precision on some of the fields, with the same
result.

FWIW, using MS-Access 2003, linked to a MAS 200 Providex Database using the
Native ODBC driver (Read-Only).

Thanks in advance for any assistance you might give.