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? Also we want to know how can we export using loadercli the unicode data of the old db and import it to an ASCII new one so we can see the table names with latest odbc drivers in access. Thanks in advance, Josu. ---------- Forwarded message ---------- From: Josu <[EMAIL PROTECTED]> Date: Mon, 8 Nov 2004 17:27:31 +0100 Subject: Using ODBC driver v.00.19 To: [EMAIL PROTECTED] Hi, i have this problem now .... im trying to map/use to import/export data using the latest ODBC drivers on windows2000 from/to the latest database version .19 When i try to see the database tables it only shows D,D,D,D,D,D,D,D,D,D........ and then S,S,S,S,S,S,S,S ........ These are from our DBA and SYS but the entire name is not shown, only the first letter. The database instance with this problem has been converted from 7.5.00.08 and works well from JDBC and SQL Studio. Anyone knows a fix? Thank u all, Josu. -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
