Problems with Special characters in AXIANT Thin Client

[Peter Bateman]

Tim:

  You can change the code page that is running on your PC.
  You want to try it. But if ORACLE is working correctly you may also need 
to change
  your NLS_LANG setting.
  I think you need to find out exactly in what code page the C-ISAM data is 
written.

  You may have to write you own conversion routines.
  PROCEDURE OUTPUT  C-ISAM-STRING
  BEGIN
      DO EXTERNAL CONVERT_TO_WINDOWS( C-ISAM-STRING, C-ISAM-WINDOWS )
      LET FIELDTEXT = C-ISAM-WINDOWS
  END
A few years ago Cognos created an .ini file entry to allow Interbase to do 
the data conversion.
However, I don't if there exists a similiar function for C-ISAM.

Good Luck,
Peter Bateman


>From: Frederiksen Tim <tifre@wmdata.com>
>To: "'powerh-l@lists.swau.edu'" <powerh-l@lists.swau.edu>
>Subject: Problems with Special characters in AXIANT Thin Client
>Date: Fri, 1 Aug 2003 13:45:46 +0200
>
>Hello,
>
>I have a problem with special danish characters, when retrieving data from 
>a
>CISAM table stored on AIX/UNIX server.
>The tables a accessed throw AXIANT server on the UNIX,  to a thin Windows
>AXIANT client.
>
>I think the problems is, the CISAM files are stored in a UNIX 8-bit ACSII
>character set,
>and are not converted into a windows characterset when send to the AXIANT
>client.
>
>I had the same problem with our ORACLE base but setting the variable
>NLS_LANG into a windows character set
>in the PH8INIT file was the solution. (our ORACLE base is also in a 8-bit
>ASCII characterset )
>
>Since we are converting a POWERHOUSE application, we can't just convert the
>CISAM datafiles into
>and windows characterset, because we still want the POWERHOUSE application
>running.
>
>We need some kind of setup that converts data on run time.
>
>Regards
>Tim Frederiksen
>
>

_________________________________________________________________
STOP MORE SPAM with the new MSN 8 and get 2 months FREE*   
http://join.msn.com/?page=features/junkmail