Hi Josu, > -----Original Message----- > From: Josu [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 9. November 2004 11:52 > To: [EMAIL PROTECTED] > Subject: Fwd: Using ODBC driver v.00.19 > > > We have currently discover that the problem is for UNICODE setting on > the database!, if we export the catalog using loadercli to another db > without unicode setting quitting all the unicode in the tables > created, ACCESS shows all the table names! > > This is weird because we have been using this db for nearly a year in > UNICODE mode with version 00.08 of ODBC drivers and database kernel > and it worked always fine, the problem has appeared with version 00.19 > of kernel and ODBC. > > This is a known issue?
What exactly? Which ODBC driver do you use? If, e.g. you work with the ASCII-driver (sqlod32.dll) then the data will be implicitely converted to ASCII. If this is possible (since no "real" Unicode is in there) you don't notice anything from having a Unicode DB. FYI, SQLStudio uses always the Unicode ODBC driver (sqlod32w.dll). If you think, that really the problem lies in the ODBC driver, please use odbcte32.exe or odbc32w.exe (from Microsoft) to reproduce the problem. Especially what kind of conversion is used. Regards Thomas ---------------------------------------------- Dr. Thomas K�tter SAP AG, SAP Labs Berlin Do you know SAP^H^H^H MaxDB ? www.mysql.com/products/maxdb www.sapdb.org -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
