HI All,
My report runs fine, and contains some large calculations. Just after I had finalized it I went into my SQL Server 2000 database and tried to edit one of the tables and received the error:
[Microsoft][ODBC SQL Server Driver][SQL Server]
Arithmetic overflow error for type varchar, value = "blah"
[Microsoft][ODBC SQL Server Driver][SQL Server]
The statement has been terminated
Since this problem did not exist before I ran the report, I know that it is connected to one of the calculations I ran. Maybe something is being divided by 0, etc. So I went into all the sub-reports and main report and commented out the calculations - Because, and here's the kicker, even though I ran the report against the development database, the live database was affected as well. Both instances are exact mirrors of each other, same table names, etc. Either way, the report no longer performs any calculationsbut the databases are both still generating this error. I went table by table verifiying which tables are affected and there are only two, with their columns that are datatype real. Any editing of a value in those columns, generates this error. I was wondering if anyone knows what is going on and how I can fix this?
My report runs fine, and contains some large calculations. Just after I had finalized it I went into my SQL Server 2000 database and tried to edit one of the tables and received the error:
[Microsoft][ODBC SQL Server Driver][SQL Server]
Arithmetic overflow error for type varchar, value = "blah"
[Microsoft][ODBC SQL Server Driver][SQL Server]
The statement has been terminated
Since this problem did not exist before I ran the report, I know that it is connected to one of the calculations I ran. Maybe something is being divided by 0, etc. So I went into all the sub-reports and main report and commented out the calculations - Because, and here's the kicker, even though I ran the report against the development database, the live database was affected as well. Both instances are exact mirrors of each other, same table names, etc. Either way, the report no longer performs any calculationsbut the databases are both still generating this error. I went table by table verifiying which tables are affected and there are only two, with their columns that are datatype real. Any editing of a value in those columns, generates this error. I was wondering if anyone knows what is going on and how I can fix this?