Special Character Set: Client SDK and ODBC issue...
Posted in 2000
Topics: Connectivity: ODBC / JDBC / .NET, Internationalization & Character Sets
Hello, I've a courious problem when I try to establish an ODBC connection (using the Intersolv 3.10 driver present in the ClientSDK 2.50 for WinNT) after the login window apperas a message box that shows: "The specified table ('nform'x.sysusers) is not in the database" Obviously the correct system table is informix.sysusers that is present! The matter is that the database has been built using the DB_LOCALE set to tr_tr.8859-9 (the GLS char set for Turkey) and also on the client there is the CLIENT_LOCALE set to tr_tr.8859-9 (I want to see the correct turkish char. on my client!) But it seems that the system translate ALL even the tables' names... causing my problem!! I've already ask to Informix for the CD-ROM with the full "International Language Settings" to use the conversions tables to translate back from turkish to another char set in which the "i" of informix.sysusers is a real "i" and not an "'" but the only translation available is from tr_tr.8859-9 to en_us.unicode but when I set as CLIENT_LOCALE en_us.unicode on my WinNT and I try to get a connection (linking a table via ODBC with MSAccess or BRIO or other tools) I get the error messages "Memory allocation failed"!! Are we really facing a limit of the informix support for the extended chercater sets?!? Can someone help me, it would be great!! Thnaks a lot for the attention, S.F.