![]() ![]() ![]() Since all drivers from 12 to 17 trigger the chained option, we went back to the version 9 driver, which you have to manually add a reference to the dll to. If this fails we will have to change the way the code is retrieving the data so as to not trigger the timeout. We are trying to connect because via ODBC a simple query times out, so we want to try changing the driver (using SA objects instead of ODBC objects). No one knows how to upgrade the database or the server. I don't know if the database does not support it or the server is the one that doesn't. It keeps doing it even in version 17, and I don't know how to stop it from doing that on this connection to this database. From version 5 to version 12 something changed, and when trying to open an ADO.NET connection, it tries to execute a CHAINED=on parameter after opening. SQL Anywhere used to come bundled with Sybase Powerbuilder, and now is the property of SAP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |