Re: Character Sets

Your solution lies in GLS (Global Language Support). This is available on the HP 7.23 db, not on NCR. At the 7.14 timeframe they called it NLS (National Language Support) which worked somewhat differently. Simply go to your manual store to find the GLS manual or go to http://www.informix.com/answers and download the GLS manual. All you ask for can be done, but it does require a little study and work. When you think about it it's prety stupid that you aren't allowed to insert simple 8 bit characters in the way you do it, but that's the way of the americans when it comes to anything foreign. Just to clarify your problem a little: You can insert an 8 bit character, but it can't be part of a quoted string. If your statement somehow includes a quoted string with such a character (which it probably does when you prepare and execute it in PowerBuilder). With this explanation it simply becomes even more stupid, but that's the way it is. Please do complain to Informix. This behaviour may be part of some standard or whatever, but it shouldn't be there. What GLS gives you in this respect is the ability to sort correctly according to the rules of your character set. If you do not enable GLS you will get sorting according to the binary value of each character. That is however an additional feature that is not allways important. There are other features of GLS as well of course. Read the manual. On Wed, 11 Feb 1998 02:04:34 GMT, jharris@westpac.com.au (Jason Harris) wrote: >Dear All, > >I have a problem: > >We have an insert statement that includes the character hex A9. The >statement works on NCR running 7.14, but on HP running 7.23 we get an >-202 error. The column to contain the value is type varcher(255). > >The insert statement is executed from a powerbuilder application using >the i-net client. The program builds the string and executes it using >EXECUTE IMMEDIATE. It is not prepared and executed using host >variables and place holders. > >We can insert this value into the table using the dbaccess load >command on HP 7.23. > >The problem is that the code is deployed on approx 1500 workstations >in branches around Australia. This will be a major show stopper with >our upgrade as once we change to HP all branches will cease to work. >Changing the code at the branches is not an option. > >What we need is a solution that can be implemented on the server side, >such as enabling a character set that includes this character but does >not disable the current en_us character set we are using. Or any other >solution that we can implement without changing the code. > >As part of the migration we will be copying all data from NCR to HP. >So if a character set exists then this may be an option. > >Regards, > >Jason > > Nils Myklebust NM Data AS Norway E-mail: Nils.Myklebust@nmdata.com