May 20, 2013 at 7:03 am
Dear Gurus,
We have facing following issue as details are mentioned below. Your kind help and support is needed.
Details:
We have migrated the application from Power Builder 9.0.3 that connects to a MS-SQL Server 2005 to Power Builder 12.5 that connects to MS-SQL Server 2008 R2 with Collation SQL_Latin1_General_CP1_CI_AS.
In PB 9.0.3 with MS-SQL Server 2005 the application displays & save the international characters (Korean) correctly but after migration the application is displaying the same international characters (Korean) as Junk characters.
We are using SNC SQL Native Client interface with following parameters.
SQLCA.DBMS = "SNC SQL Native Client(OLE DB)"
SQLCA.LogPass = <Mypassword>
SQLCA.ServerName = "ServerName"
SQLCA.LogId = "UserID"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Database=DBName,Provider='SQLNCLI10'"
Now, when we connect to the server the international characters are displayed as junk as shown below.
¼¿ï½Ã¼¿ï½Ã
Instead of the Korean language as shown below.
서울시서울시
Then we added the AutoTranslate parameter:
SQLCA.DBMS = "SNC SQL Native Client(OLE DB)"
SQLCA.LogPass = < Mypassword >
SQLCA.ServerName = " ServerName "
SQLCA.LogId = "UserID"
SQLCA.AutoCommit = False
SQLCA.DBParm = "Database='Databasename',Provider='SQLNCLI10',ProviderString='AutoTranslate=NO'"
After applying the AutoTranslate keyword still the issue persists and the application show the international characters (Korean) as junk characters.
We also try the same AutoTranslate keyword with PB12.5 and ODBC combination with the following
dbparm:
SQLCA.DBMS = "ODBC"
SQLCA.AutoCommit = False
SQLCA.DBParm = "ConnectString='DSN=test1; UID=UserID; PWD=<MyPassword>; Autotranslate=no'"
When tested with the same environment of PB12.5 and MS-SQL Server 2008 , the application displays the International characters (Korean) correctly as shown below.
서울시서울시
Apparently Autotranslate (or Auto Translate) property is working perfectly with ODBC but not with OLE DB. Although the SQL native client OLE dbparam accepts the autotranslate property but the international characters(Korean) still show as junk.
Kindly help on this if we are missing any configuration or provide any work around to achieve the correct behavior regarding the international characters (Korean) with PB12.5 and MS-SQL Server 2008 R2 using SQL native client OLE DB.
Thanks
Adeel Imtiaz
May 21, 2013 at 4:47 am
ANY SOLUTION ??
February 17, 2016 at 5:45 am
Any Solution for this?
February 17, 2016 at 7:27 am
SQL_Latin1_General_CP1_CI_AS isn't really an unicode character set. So it is possible that it displays Korean differently when connecting with another client.
Perhaps a difference on the client side
February 17, 2016 at 7:44 am
Seems like you isolated it to a driver issue. If memory serves, the OLE DB driver in SNAC actually leverages the ODBC driver behind the scenes so the problem may be in the OLE DB layer. Can you switch to using ODBC driver directly, which you proved works correctly? Microsoft is slowly but surely moving away from OLE DB and recommending ODBC for new development anyway.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
February 18, 2016 at 2:59 am
My problem is slightly different. From the database i get the Korean characters as is. But on the UI screens, for text labels etc, text should shown in Korean, But it is showing ASCII values.
February 18, 2016 at 3:20 am
bh.shalini (2/18/2016)
My problem is slightly different. From the database i get the Korean characters as is.
Earlier you said you were not, from the new database via the OLE DB Driver. Are you now saying the database is fine and you get proper data via the OLE DB driver?
But on the UI screens, for text labels etc, text should shown in Korean, But it is showing ASCII values.
If the OLE DB driver is in fact delivering proper data then it seems the issue is isolated to the UI, so you should focus your efforts there.
edit: fix quote tag
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
February 18, 2016 at 5:09 am
Orlando Colamatteo (2/18/2016)
bh.shalini (2/18/2016)
My problem is slightly different. From the database i get the Korean characters as is.[\quote]Earlier you said you were not, from the new database via the OLE DB Driver. Are you now saying the database is fine and you get proper data via the OLE DB driver?
Shalini: That's correct.
But on the UI screens, for text labels etc, text should shown in Korean, But it is showing ASCII values.
If the OLE DB driver is in fact delivering proper data then it seems the issue is isolated to the UI, songou should focus your efforts there.
Shalini: It is only with UI screen display. Any suggestions please.
February 18, 2016 at 5:55 am
Seems you've ruled out a database problem. Maybe contact the Power Builder folks or post your question on a Power Builder forum.
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply