You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My .net application works fine on 32-bit windows operating systems, but gives 'arithmetic exception error' when uploaded to 64-bit windows (tried and tested on windows 7 and windows 2008 server with similar results) operating system. After much investigation, I have narrowed the problem with the ODBC driver. Can someone please fix the bug::
1. When using the datareader (while (datareader.read()), if the row has a null value it breaks, with an arithmetic overflow exception. I proved it also when I trap this code in a {try catch}.
2. Queries run fine in all tables that don't have a null value or if I force to return the "" (empty) string in a select command (select case when veh_model is null the '' else veh_model). This query is not pleasant, especially when I know I have a massive database to work with and changing a huge application into .net where I would like to reuse the previously working queries.
3. To reproduce the error, you may run a helloworld application on a small firebird database with one column having a null value. the operating system is windows (any version) 64 bit.
The text was updated successfully, but these errors were encountered:
Submitted by: jaffar chiosa (cjaffar)
Attachments:
OdbcFb.zip
Votes: 1
My .net application works fine on 32-bit windows operating systems, but gives 'arithmetic exception error' when uploaded to 64-bit windows (tried and tested on windows 7 and windows 2008 server with similar results) operating system. After much investigation, I have narrowed the problem with the ODBC driver. Can someone please fix the bug::
1. When using the datareader (while (datareader.read()), if the row has a null value it breaks, with an arithmetic overflow exception. I proved it also when I trap this code in a {try catch}.
2. Queries run fine in all tables that don't have a null value or if I force to return the "" (empty) string in a select command (select case when veh_model is null the '' else veh_model). This query is not pleasant, especially when I know I have a massive database to work with and changing a huge application into .net where I would like to reuse the previously working queries.
3. To reproduce the error, you may run a helloworld application on a small firebird database with one column having a null value. the operating system is windows (any version) 64 bit.
The text was updated successfully, but these errors were encountered: