We help IT Professionals succeed at work.

Numeric Field Overflow error 3349

Fordraiders
Fordraiders asked
on
I'am trying to Append an Excel spreadsheet to an Access Table.

I keep getting an error 3349 numeric data overflow error.
I have tried to change almost everything.
Can't seem to find the problem.
Not much on the net.

any help??

Thanks
fordraiders
Comment
Watch Question

sounds like you're trying to put a large value into a column that isn't enabled for large values.  For instance, you're putting a very large number into an integer field or byte field.

Author

Commented:
escheider,
That's what  is weird.
I have resaved the numeric fields as text but they appear to only have 10 characters at the most.
Do you have any examples of your data, and how do you have your column(s) declared (String,Numeric, etc?)
Ryan ChongSoftware Tead Lead / Business Analyst / System Analyst / Data Engineer
CERTIFIED EXPERT

Commented:
Hi fordraiders,

Check your "Field Size" in your Field's Property, Maybe you need to Change it to allow bigger value.
Gee, sounds like something I've said.
Ryan ChongSoftware Tead Lead / Business Analyst / System Analyst / Data Engineer
CERTIFIED EXPERT

Commented:
ya, just point fordraiders to the right way..
Sounds like you have a field size problem  ;)

JUST KIDDING.

Are you importing manually or thru code?

Does it get to the point of building an ImportErrors table?

dill

Author

Commented:
Here are the scenarios:

1. Linking to an excel spreadsheet.
2. Running an Append query into an Access Table.
   -Access table fields are NUMERIC
   -when I first run the query it works fine.
   -when I try to run the query again I get the
"ERROR Numeric Field Overflow"

THIS IS WHATS WEIRD!
If I compact and repair the database.
Then run the query.
It works fine.
But will NOT execute on the second try  UNLESS I compact.

Thanks
fordraiders
Ryan ChongSoftware Tead Lead / Business Analyst / System Analyst / Data Engineer
CERTIFIED EXPERT

Commented:
Hi,

Are the Data Type of your Primary Key is a Autonumber? Could it be the problem?

> Correct me if i'm wrong.

Author

Commented:
No Autonumber keys
Thanks
fordraiders

Author

Commented:
To All,
I have just learned that this data in the excel spreadsheet, may have come from SAP system.
Has anyone had any experience with this?

Thanks
fordraiders

Commented:
Hi!

Probably this problem was resolved but there goes my comments anyway...

When a link to a spreadseet is made, Access analyzes the first 8 rows to set the data type for that column.
If that 8 first rows type does not represent the others then this problem occours becouse Jet Engine found a value that does not fit in the data type. In the Datasheet View the value for those cells is seen as #NUM!.

My work around: manipulate the source spreadsheet to help Access "guess" the correct datatype. There is no need to validade every row in the column, just the first 8 ones.

Best regards,


Cristiano.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.