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