1. Glenn Barber
  2. PowerBuilder
  3. Tuesday, 29 August 2017 19:00 PM UTC

We have a PB app in 12.6 (moving to PB 2017) which is largely used by users in English

However we have the need to enter some information (usually foreign language names) in native Character sets - such as Chinese, Korean, Eastern European.

Usually the users want to cut and pase the information from excel sheets where the information appears correctly in windows.  It appears correctly when intially pasted but does not seem to be stored or redisplayed correctly.

We are using SQL Anywhere 16 as the database.

We have found that just defining the data fields as nvarchars doesn't seem to be a solution.

 

 

 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 29 August 2017 22:07 PM UTC
  2. PowerBuilder
  3. # 1

Hi Glenn;

   Since PB has been Unicode compliant since v10.x and utilizes the Microsoft UTF16LE standard, any data stream saved in a column of type: NCHAR, NVARCHAR or Long NVARCHAR - that began its life in MS-Windows in UT16LE format - should thus be re-creatable for display upon any update / retrieve scenario.

   As a test, I just created a new table in SA v17 called Chris, as follows:

   I then created a DW object that used the columns in the table Chris, as follows:

     As you can see from the above, adding, updating & then retrieving the Unicode datum was successful in either Korean (data1), Japanese (data2) or Russian (data3).

PS: I used the PB Demo DB V2017 Unicode example SA database that came with the PB 2017 installation for this test.

HTH

Regards ... Chris

 

 

  

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.