Re: Spanish local characters + Informix

It sounds like you have not set up GLS (or NLS if it's an older server). On servers prior to some version I don't know (7.2 something I believe) you had to set up GLS support even though the default locale is supposed to use the 8 bit 8859-character set. There was a bug that made it accept only 7 bit characters on input (via 4GL/dbaccess and similar tools). 4GL doesn't realy support GLS (or NLS) until realease 7.20, but it will still display the 8 bit characters correctly and allow input of them providing your terminal or terminal emulator is capable of handling them. For this it is however required that you set the DB_LOCALE environement variable before you create the database. It's CLIENT_LOCALE that isn't supported by 4GL, but we set it to the same as the DB_LOCALE anyway. There is also a SERVER_LOCALE variable, but I know no reason why anyone would realy want to set that. There is unfortunately no way of changing the GLS locale of a database even if you know that no data or indexes needs be updated as a result of such a change. You have to create a new database wile the correct value for DB_LOCALE is set. You should be carefull about utilizing GLS further than setting the variables as above. There have been reports that using the nchar/nvarchar datatypes to get "correct" ordering of indexes significantly slows down both index creation, updates and selects. This I think is due to a bug in how Informix has implemented the suport of this in the engine. On Tue, 21 Jul 1998 19:23:08 +0200, "A.P." <road@apdo.com> wrote: >Hi, >I have problems getting Informix to display (either in dbaccess or in my >4gl application) the Spanish characters. I mean it does displays the >ones I loaded with a bulk load, but not the ones I type interactively. >I'm using an SCOANSI emulation on top of Solaris 2.6. There's no problem >to get the chars in the OS prompt. >Any idea? >TIA. > Nils Myklebust NM Data AS Norway E-mail: Nils.Myklebust@nmdata.com FAQ at: http://www.iiug.org/techinfo/faq/faq_top.html (Now with ODBC info under "Third party products".)