RE: ODBC & Umlauts

Funny you should mention that -- been having some mixed victories there myself: You need to set the environment variables DB_LOCALE and CLIENT_LOCALE For website purposes, and running off an NT server, our values are: DB_LOCALE=en_us.PC-Latin-1 CLIENT_LOCALE=en_us.8859-1 You'll have to find the right magic spells for your own purposes. On UNIX, supposedly you can set the values in .odbc.ini I say supposedly because the FM also says on NT you can set them with setnet32, and that hasn't worked. What got it working on our development box was the ODBC driver itself had an Environment tab in its configuration, and you could tell it directly what to use. Hope that helps -- I could use some help myself: our live system has an INTERSOLV ODBC driver which does not let you set environment, and so far we have not been able to get it to listen -- we have set the variables in setnet32 AND in the System variables on the Control Panel, but no luck. Anybody got any suggestions? > -----Original Message----- > From: ksterker [SMTP:ksterkerNOksSPAM@topmail.de.invalid] > Sent: Thursday, April 06, 2000 5:37 AM > To: informix-list@iiug.org > Subject: ODBC & Umlauts > > We've got a SE 7.24 running on AIX 4.1.5. When accessing > the DB via ODBC from NT 4.0 all the umlauts (dv|DV\\_ etc.) > are messed up. > > The AIX locale is en_US, NT is the German version. > > Is there a way to have the ODBC driver transform the UNIX > character set to the proper Windows Codepage? > > > K. Sterker > > > * Sent from AltaVista http://www.altavista.com Where you can also find > related Web Pages, Images, Audios, Videos, News, and Shopping. Smart is > Beautiful