• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Best practice for Pb apps storing characters in unicode to sql server?

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved Best practice for Pb apps storing characters in unicode to sql server?

  1. How-to
0
Votes
Undo
  1. Heino Hellmers
    Heino Hellmers
  2. PowerBuilder
  3. Tuesday, 29 March 2022 18:31 PM UTC

Hi

we are on Pb2021 connecting to SQLServer 2019 by new Microsoft OleDB Driver.

In past we also used SNC, sql server native connect.

We need to store  unicode characters like Ą, Ć, Ę, Ł, Ń, Ó, Ś, Ź, Ż

Our db column datatypes are nvarchar for sql server database to save unicode characters but the database saves different  characters. to db. This seems to be because we do not use ncharbind=1.

As far as we know we have to set dbparm to ncharbind=1 and to make this work in addition also disablebind=0.

But disablebind =0 has different bad side effects on our program. Today we are using disablebind=1.

Some best practice to save unicode data to sql server by pb program?

Is using ncharbind the right way to do?

TIA

Heino Hellmers

How to Prevent a Window from Minimizing
How to Deploy .Net Assembly along with Power Build...
Responses (1)
Arnd Schmidt
Arnd Schmidt Accepted Answer Pending Moderation
  1. Wednesday, 30 March 2022 22:26 PM UTC
  2. PowerBuilder
  3. # 1

Hi Heino,

have you already looked already into that "solution".

https://community.appeon.com/index.php/qna/q-a/store-chinese-character-on-nvarchar?limitstart=0#reply-31725

It's brute force and has some pitfalls, but might be a good start to modify the Datawindow generated SQL Statements in the SqlPreview Event.

hth

Arnd

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.