"Auto Translate" with PB and MSSQL in OLE DB not WORK

1
0
-1

I had tried to use the "Auto Translate" with PB and MSSQL in OLED DB to 
MSSQL, however I had found this parameter do not work !
I had tried this in PB 12 and PB2017 , also tried with MSSQL2000 and MSSQL2008, 
but the it is do not work properly.

the connection info list as :

// Profile lib_sys
SQLCA.DBMS = "OLE DB"
SQLCA.LogPass = <********>
SQLCA.LogId = "sa"
SQLCA.AutoCommit = False
SQLCA.DBParm = "PROVIDER='SQLOLEDB',DATASOURCE='ANDREW',PROVIDERSTRING='Auto 
Translate=false;Database=libsys',DelimitIdentifier='No'"

I had tried this in C#, "Auto Translate" work fine !

So do anyone have idea about what's wrong with this parameter in PB/MSSQL

Question Tags: 

Answers

Roland Smith answered "Auto Translate" with PB and MSSQL in OLE DB not WORK

1
0
-1

PowerBuilder is Unicode only and therefore automatically converts string data to Unicode when retrieving it from the database.

xiaolong.qin_33265's picture

Hi Roland ,

Thanks ,Could you please give me more advice ?

Currently we have a few of APPs with PB8+SQL6.5 which planned to migrate to PB2017 + SQL2016 .

PB8+SQL6.5 with MSS connection ,if Non English character such as Japanese stored in MS DB as char/varchar would display correctly in DW .

After migration ,as MSS not support from PB10 ,we tried OLE / SNC connection ,but the Non English characters always are unreadable.

Based on your reply ,PB auto convert string to Unicode ,any configuration existed on this ? or any idea that we can figure it out to make Non English characters readable?

 

Thanks very much .

 

Alfredo Aldama answered "Auto Translate" with PB and MSSQL in OLE DB not WORK

1
0
-1
Hola, Porque repetir la pregunta de hace 11 años o más sustituyendo solo las versiones? O es coincidencia? Lo dudo. Has escuchado el concepto de microservicios en el puedes armar el sistema integral (SOA) con subsistemas hechos con diferentes lenguajes. Posdata: con powerbuilder he hecho un crud con 5 líneas en 3 minutos y migrado con un click Y volviendo a tu duda también puedes al momento de migrar tu base de datos hacer uso de las bondades de la base de datos es decir temas como el código de página. Saludos 在墨西哥,我们说你是一个天才

xiaolong.qin_33265's picture

Thanks Alfredo ,

Yes ,some legacy Apps are planned to migrated to PB2017 & SQL2016 . More substituting only the versions and much better if less codes change .

Please correct me if my understanding is wrong ,for unreadable characters ,the solution is using PB to write a crud with ODBC connection to get data then update to updated Unicode columns ?

 

Thanks in advance .

Alfred Aldama's picture
I think there are many ways to do, however I use that, in 2008 I was working with a migration from 6.5 to 2008, reverse engineering for database, makeup the properties, forward engineer and I do a program for read db source & write on dB target, easy, quickly and no problems for characters. (by example on blobs )
Alfred Aldama's picture
I think there are many ways to do, however I use that, in 2008 I was working with a migration from 6.5 to 2008, reverse engineering for database, makeup the properties, forward engineer and I do a program for read db source & write on dB target, easy, quickly and no problems for characters. (by example on blobs )
xiaolong.qin_33265's picture

Thanks Alfredo .will try this way . smiley