Usually, I start dbisqlc with an appropriate connection string.
However, when trying to connect interactively, I can only choose among ODBC datasources of the version, i.e. dbisclqc V8 lists only V8 DSNs, dbisqlc V12 lists only V12 DSNs, dbisqlc V11 only V11 DSNs. (As such, it' sno new problem.)
In contrast, DBISQL seems to do so by default, too, but has this "search" button to look for different DSNs.
Question: Have I met another dbisqlc restriction, or can this by changed by some option?
asked 21 Oct '10, 09:33
dbisqlc (actually dbconX.dll) does explicitly filter the DSNs to those that are defined to use the SQL Anywhere ODBC driver of the same major version as dbisqlc and there is no way to get around that behaviour. I can only guess that the filtering was done because we didn't want to show non-SQLAnywhere DSNs. What would you expect -- would you want it to show all DSNs or just SQLAnywhere DSNs?
I also found that the 64-bit version of dbisqlc doesn't populate the DSN list at all.
Note that dbisqlc is a dblib application and doesn't use ODBC when you use a DSN. The DSN is only used to pick up connection parameters.
answered 21 Oct '10, 20:30
I've had that problem too. If you know the data source name you might overcome that limitation with
answered 21 Oct '10, 15:54