Hello all.

I've been trying to talk to a DBISAM database via ODBC with Sun's JDBC-ODBC bridge. I keep
getting failures at various points with the following message:

[Elevate Software][DBISAM] Floating point division by zero

The connection is made correctly - I'm using version 4.2.4 of the ODBC driver (trial
version), and the trial version banner appears. The errors occur while reading the data.

Some other messages from the driver before the fatal error are:

12:45:59,212 WARN  [JDBCExceptionReporter] SQL Error: 11047, SQLState: HY000
12:45:59,212 ERROR [JDBCExceptionReporter] [Elevate Software][DBISAM] Floating point
division by zero
12:45:59,222 WARN  [JDBCExceptionReporter] SQL Warning: 0, SQLState: 01004
12:45:59,222 WARN  [JDBCExceptionReporter] [Microsoft][ODBC Driver Manager] Data truncated
12:45:59,222 WARN  [JDBCExceptionReporter] SQL Warning: 0, SQLState: 010
12:45:59,222 WARN  [JDBCExceptionReporter] [Elevate Software][DBISAM] String data, right
truncated

Has anyone had any experience of using DBISAM with Java? The full set up is Java 1.5.0 and
using Hibernate 3.2.

Thanks,
Richard.

Richard,

<< I've been trying to talk to a DBISAM database via ODBC with Sun's
JDBC-ODBC bridge. I keep getting failures at various points with the
following message:

[Elevate Software][DBISAM] Floating point division by zero

The connection is made correctly - I'm using version 4.2.4 of the ODBC
driver (trial version), and the trial version banner appears. The errors
occur while reading the data. >>

Could you send me the Java code that you're using ?  I can at least trace
things and see what is going on.  I suspect that the floating-point mask for
the processor is being changed or something similar that is messing with the
Delphi RTL.  DBISAM's ODBC driver only does division is 2 places, and both
of those places are places where it is impossible to divide by zero.  One
divides by a constant of 16 and the other divides by 1 taken to the Nth
power (used for numeric struct processing in ODBC).

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim.

I've sent you an email with details on getting the code to try. As the problem is way
below the level of my source code, there is no particular snippet I can post here.

Thanks,
Richard.

Richard,

<< I've sent you an email with details on getting the code to try. As the
problem is way below the level of my source code, there is no particular
snippet I can post here. >>

Got it, thanks.  I will let you know what I find out.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim.

Any luck with this Java/ODBC issue?

Thanks.

Richard,

<< Any luck with this Java/ODBC issue? >>

Frankly, it got lost in the shuffle with the EDB release.  I'll see if I can
revisit it next week.  I'm pretty much committed to working on EDB 1.01
Build 2 all weekend and into Monday/Tuesday of next week.

--
Tim Young
Elevate Software
www.elevatesoft.com

I've just tried the latest build of the ODBC driver (4.25 build 7) on the offchance this
problem has fixed itself. It hasn't.

Ta,
Rich.

Richard,

<< I've just tried the latest build of the ODBC driver (4.25 build 7) on the
offchance this problem has fixed itself. It hasn't. >>

It wouldn't - it hasn't been addressed because, frankly, I don't think it's
an issue with our driver that can be fixed.  It hasn't manifested itself in
any other fashion with any other type of front-end, nor can I get it to
happen here in a general fashion.

--
Tim Young
Elevate Software
www.elevatesoft.com