MAXDB 7.9 ODBC SQLPrepare issue

[Former Member]

Hello,

with MAXDB 7.6 I could use the following command sequences with ODBC

SQLPrepare(SELECT ...)

SQLBindParameter()

SQLExecute()

SQLFetch()

SQLCloseCursor()

and then again

SQLExecute()

SQLFetch()

SQLCloseCursor()

as often as I wanted.

With MAXDB 7.9 (64-bit, Windows) the statement apparently has to be re-initialized completely after SQLCloseCursor().

Am I correct in attributing this behaviour to MAXDB?

Is there a chance that this will change again?

Peter Willadt

[thorsten_zielke]

Hi,

hmm, this should work in 7.9 as well. Please trace that sequence with a MaxDB kernel trace (vtrace) enabled - you can use this link for upload:
https://share.sap.com/a:gns0cg/MyAttachments/R.c63f8d22-fde0-4743-a2e1-79d512474878/

If you want, you can also add an ODBC trace, but this would be optional at the moment 🙂

Thorsten

[thorsten_zielke]

Ok, the vtrace shows that the database kernel has the correct result for the second 'execute', so the error must be in the used ODBC driver version.

Please execute with ODBC trace enabled and vtrace option 'trace long on'.

For upload, just use this new container:

https://share.sap.com/a:gns0cg/MyAttachments/R.b98fa1ad-3465-4b17-b30f-bb104478e168/

Also, please let me know which version of MaxDB kernel you are using and the ODBC version.

Thorsten