Like Pb7/PB9 character set with ANSI, but PB11 abnormal with the UNICODE, now will be garbled words in Chinese! You have what way???
CodePudding user response:
Did not encounter this problem!From PB9 upgrade is very normal!
CodePudding user response:
What call PB11 abnormal use UNICODE...When you translate, there is an option called auto convert DBSC XXXX
On the hook
CodePudding user response:
The pb when connecting to the oracle database can directly connect, why garbled wordsDoes not support the low version of the ah, I am using is 8
CodePudding user response:
Can directly connect,You said the code is pb itself, or the data layer,
CodePudding user response:
The code are caused by the pb pb10 later processing are using unicode characters, but not previous versions,Who has seen me this post:
http://topic.csdn.net/u/20080703/08/33906f94-988c-40cc-aa0e-8445bf951081.html
Read the should understand some,
CodePudding user response:
The SQLCA. Try DBParm="DisableUnicode=1"CodePudding user response:
To regenerate once!CodePudding user response:
Used pb11CodePudding user response:
It is related to the database character setCodePudding user response:
Haven't met this problem, best backup source file before upgradingCodePudding user response:
The SQLCA. DBParm="DisableUnicode=1" to solve the problemCodePudding user response:
Program using the API will appear this problem basically, that's all right, behind the API to add; ANSI, pb in your helpCodePudding user response:
The SQLCA. DBParm="DisableUnicode=1" in the problem solving,CodePudding user response:
I'm using the pb10, the data window just access to the system table, show the code in Chinese? Who know how to return a responsibility?CodePudding user response:
Haven't rise, make a mark, standby,CodePudding user response:
11.5 try using pb