Numeric Field Overflow

[lord of the badgers]

Grrrrrrrrr. :x

I have:
One Access2000 database
One Access 97 Back End (have to - the company is still mid rollout of 2000)

I have maketables in A2000 dbase which write to the A97 dbase - it works OK for two of em, but one now refuses to work. did before. just get the bloomin Numeric Field Overflow message. It deletes the old table, but the darn thing won't make the new one!



ideas? (i'd like to be sorted by thursday...!) thanks guys..

 

[bat17]

if the tables are the same just delete the data not the table and append the new data into it.

HTh

Peter

 

[lord of the badgers]

oh aye,.... i'll give it a go...

 

[lord of the badgers]

oh aye,.... i'll give it a go...

whatever i do i get this bloomin error.

did as you suggested. same result.
i have criteria in the query..maybe that's why?

why is it i can make a table ok in the first intsnace. I run it again, get the error, it deletes the table (of course), i run it again, Numeric Field...

however, if i slightly rename the table to be made, run it, run it again (and get the error but delete the table), then re-name it back to the original table, run it again, it's ok.

it's just like this big loop of sh1te.... very annoyed with it all now.

 

[bat17]

Have you tried running a repair and compact on the database? might just help

Peter

 

[SydneyGeek]

Check the data types on the table. Specifically, the Numbers -- you may have an Integer (limit 32K) that needs upgrading to a Long (limit 2Bn).
A bit like Row numbers in Excel...

Denis

 

[lord of the badgers]

we found it in the end (thanks tho!)..

first field= long integer, second=text

i put an IS NOT NULL criteria in 1st field, and "<>'blah blah' " in the second. the buffer (or whatever it is) kept getting thoroughly freaked by this...

lesson learnt!

 

[lord of the badgers]

Just to bump this back up,

I've been receiving the Numeric Overflow message on another project.

It would seem that Numeric Field Overflow occurs when you run a query on linked spreadsheets into Access.

My guess is that it is hitting the memory contraints of Excel, rather than data type problems, but one thing that is common (there are two other threads on this issue) is that there's no equivocal answer.

any thoughts?