Numeric Field Overflow Error

[bodylojohn]

Hello everybody...

Does this Error look formiliar???

"Numeric Field Overflow 3349"

The case is:

I have a .txt file wicht I link to the database.
If I run a query based on that .txt file I get the Error.
...BUT sometimes if i close the database and compact it it works..

??????????????

Thank you for your help in advance...

 

[Oldsoftboss]

My guess is somewhere you will have a "Dim a as Integer"
Try changing it to Dim a as Long.

As to "Sometime after compacting it works" well ?????
It is Access.

Dave

 

[Ron_dK]

I have a .txt file wicht I link to the database.
If I run a query based on that .txt file I get the Error.

How many records are created by importing the txt data to your Dbase.
There is a max of 65000 records I think.
Might that cause the error ?

 

[bodylojohn]

Hello guys,

Thanks so far.

I don't use a dim a as integer.
So that could not be the problem.

I hope to hear from you guys..

So THANKS again...

 

[Ron_dK]

OK, I'll give it another shot :

Usually what the error means is that you are importing into a Numeric field that is set to Long.
You will have to change this field's type to Double instead of Long.

 

[bodylojohn]

Hello,

I also tried that and still I recieve the error..

I'm keeping my hopes up..

Thanks guys

 

[Bat17]

what is the query doing with the data?

Peter

 

[bodylojohn]

A new table is generated from the linked textfile...

Hope to hear from U guys..

 

[Ron_dK]

Note that text fields in your table are limited to 255 characters.
If the textfile that you're importing has more, change the (table) field to memo.

 

[Bat17]

OK, presumably you are using a Maketable query then. Two ideas then, either
I would change it to a normal select query and run it, to make sure you are getting the data in to the DB OK. Once that works you can then make the table using only some of the fields, increasing the number until you can piun down where the error is being generated.

Or

Don't link but use the File>Getexternal Data>Import... Wizard. this will give you control over your data types.

HTH

Peter

 

[The_Doc_Man]

What bothers me here is that linking a table to a text file means you cannot have ANY integers in the text file - if it is truly text! I.e. if the linked file is to also be human readable, ALL fields in the file must be ASCII representations - i.e. ... TEXT! This is NOT true when IMPORTING from a TEXT file because if the wizard is given a proper target field type, it can do the conversion for you. But it IS true for LINKED files. They are NOT converted. They have to be used more or less as-is.

Now if you have ALL fields in the linked table as TEXT, you CAN run a query to build your other table, where you use functions like CINT, CLNG, CSNG, CDBL, etc. as part of the converting query. And that conversion should work quite well. If you take any other appoach, you are probably mixing apples and oranges, thus giving you fruit salad. And overflows.