Hi,
I'm using a development enviroment that uses ODBC to access SQL Anywhere.
I have the following problem: when I have a transaction, and within the transaction I fetch some records, I will have read-locks even after calling COMMIT.
Searching the forums I found a possible explanation. It said that ODBC declares cursors by default with the "WITH HOLD" clause, and that even after the COMMIT call, the cursors would still be open, and thus the read locks remain.
As the user continues to use the application these read locks start to interfere, and since I really don't need them :-), I need to find a way to get rid of them.
Is there an ODBC call, or some way to effectively close all locks? Other than disconnecting I mean.
BTW, from my application I can't control how ODBC actually fetches the records....
Best regards,
Edgard