Yes, and that's apparently came into play as a result of Firebird 3's change to
return COUNT() as a BIGINT rather than integer. So the ODBC driver is declared
innocent. Thanks to all for having helped figure out what's happening.
Jonathan Finch
Principal Consultant
Rushmore Information Service
With Visual FoxPro, a column BIGINT is returned as type character, not as
type integer.
But it can be easily converted to integer, with the VAL() function.
Greetings.
Walter.
On Wed, Dec 3, 2014 at 4:02 PM, Dimitry Sibiryakov wrote:
> 03.12.2014 20:40, jfi...@rushmoreinfo.com wrote:
> > In m
Thanks for the quick reply. If the driver is working as designed, then perhaps
the issue is indeed with the client app's language. I will test further. In
any case I know I can solve the problem by CASTING the returned variable to the
type needed.
Jonathan Finch
Principal Consultant
Rushmore
03.12.2014 20:40, jfi...@rushmoreinfo.com wrote:
> In my tests of SQL statements using ODBC driver version 2.0.3.154 with the
> Firebird 3.0 Beta 1, COUNT(*) is apparently returning a character variable.
It should return value of SQL_BIGINT or SQL_NUMERIC types. Perhaps, your
software is
not
In my tests of SQL statements using ODBC driver version 2.0.3.154 with the
Firebird 3.0 Beta 1, COUNT(*) is apparently returning a character variable.
This is causing some errors in my apps that have always expected COUNT to yield
an integer, which is what version 2.0.2.153 of the driver return
