Hi, Gilbert -

It's difficult to say for certain, but typically, issues relating to incorrect characters being read, displayed or written are due to encoding differences. PB uses Unicode 16LE (LE -> Little Endian) encoding internally since PB 10.0, which was released in 2004, I believe.

I have no idea what encoding DB2 utilizes.

It's always a good idea to include the version, release and build of PB that you are using in your posts, as this can greatly affect the response(s) you may receive.

For database-related questions, it is highly recommended that you include information about the DBMS vendor (DB2, in this case), the version, and all of the properties of the PB Transaction Object (masking any sensitive values for security reasons, of course).

Best regards, John

Hi Gilbert,

Thanks for reporting this issue!

I didn’t reproduce this problem locally.

Please help provide more information:

1. What’s your PowerBuilder version?
2. What’s your DB2 ODBC driver version?
3. What is the character set or codepage used by DB2 to create the Database?

Best Regards,

Peter