Hi Norbert, > -----Original Message----- > From: Norbert Mende [mailto:[EMAIL PROTECTED] > Sent: Mittwoch, 7. April 2004 13:46 > To: Koetter, Thomas Theodor; [EMAIL PROTECTED] > Subject: AW: Problems with dynamic ODBC and iodbc on Linux > > > Hello Thomas, > > the program terminates "correctly" and the mysterious signs are the > output. > > iodbctest terminates in ODBC_Connect with a -1 and then an > error message
FYI, ODBC_Connect is no ODBC-API call (SQL[Driver]Connect would be). For ODBC, -1 as return code is the constant SQL_ERROR. > should follow. When printing out the errormessage, the debugger runs > through a "if (unicodedriver) ...". So, my assumption is, If iodbc tries to use Unicode, you should use the libsqlodw-version of the driver. This contains the full Unicode-ODBC-API (the functions ending on a capital 'W' like SQLPrepareW). > that iodbctest > tries to interpret a normal string as a unicode string (or > the other way > round) and prints it out. > > The question now is: Why does it run into that unicode part? (And why > does the connection not work) I don't know the internals of iodbc and how to force iodbc to use ASCII- or Unicode-commands. But if iodbc tries to connect with an ASCII-string interpreting as Unicode, I'm not suprised that this does not work. HTH Thomas ---------------------------------------------- Dr. Thomas K�tter SAP AG, SAP Labs Berlin Do you know SAP^H^H^H MaxDB ? www.sapdb.org -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
