Issue with ODBC connections, rows past line 65536 nulled/zeroed
Posted: Fri Oct 20, 2023 5:12 am
I have raised this with IBM Support but thought I would ask if anyone has seen this.
We have an ODBC query against a PostgreSQL materialised view which returns 72,000 rows. Using ODBC in Excel all rows come through fine. In a TI any rows past 65536(2^16) have string values set to null and numeric values set to 0 (In summary, a bunch of commas is returned). Version 2.0.9.16 / 2.0.9.18. Tried both 32 and 64 bit drivers.
Anyone seen anything like this?
We have an ODBC query against a PostgreSQL materialised view which returns 72,000 rows. Using ODBC in Excel all rows come through fine. In a TI any rows past 65536(2^16) have string values set to null and numeric values set to 0 (In summary, a bunch of commas is returned). Version 2.0.9.16 / 2.0.9.18. Tried both 32 and 64 bit drivers.
Anyone seen anything like this?