ODBC Call Failed - Numeric value out of range

[Jay]

Thanks in advance.
I have a working ODBC connection to SQL Server 2000.
Today, one of out 5 SQL tables is showing a following error.

ODBC Call Failed
[Microsoft][ODBC SQL Server Driver]Numeric value out of range (#0)

Is this server side table issue?
How can I restore connection to this table.

Thanks

 

[Tom van Stiphout]

On Fri, 25 Apr 2008 12:37:02 -0700, Jay

Let's assume the error message is accurate. That would mean that the
SQL Server table has a value that Access considers out of range for
the data type it thinks the column has.

Example: look at your linked table in design view and observe you have
a numeric field that is a Long Integer. You know that means only
values from roughly -2^31 to +2^31 are valid.
Then look at the corresponding column in SQL Server. Let's say it's a
bigint column which you know can hold much larger values.
Then the failure would occur if a bigint outside of the Long Integer
range is in the table.

-Tom.

 

[saulysw]

Jay,

I'm getting this too for one client, but not on my PC. I have checked,
and we have identical versions of Access, the SQL ODBC driver, MDAC
and we use the same database.

If I open the table directly (rather than try and change the data from
within forms) and insert a record it seems to sometimes give the error
"numeric value out of range", other times to simply flag the record as
being Deleted, and sometimes, the whole table as Deleted (which is
kind of scary to look at!). If you close and re-open the table the
insert has actually been done. Access has the correct unique index as
per the SQL (2000 in my case) table. Very, very odd.

- Saul