OracleClient
-
Hello, I am using Microsoft data provider for oracle. This is connecting to a Oracle 9i database. I would like to store and retrieve Japanese character using the Oracle client class. I have a problem right here. When i map .NET string datatype to the Varchar type of oracle client class, japanese character goes as junk characters(question marks). When i use Oracle Data Provider for .NET i had a datatype called Varchar2, where it working fine. Any one faced this problem thanks for your answer Cheers, Venkatraman Kalyanam Chennai - India "Being Excellent is not a skill, it is an attitude"
-
Hello, I am using Microsoft data provider for oracle. This is connecting to a Oracle 9i database. I would like to store and retrieve Japanese character using the Oracle client class. I have a problem right here. When i map .NET string datatype to the Varchar type of oracle client class, japanese character goes as junk characters(question marks). When i use Oracle Data Provider for .NET i had a datatype called Varchar2, where it working fine. Any one faced this problem thanks for your answer Cheers, Venkatraman Kalyanam Chennai - India "Being Excellent is not a skill, it is an attitude"
Ensure that the page is set for Unicode encoding. I had trouble with this in SQL Server. I could input Russian characters through Query Analyzer and they would store correctly in the database, but when I entered the information through my web form, nothing but question marks. I change the page encoding to UTF-8 and all was well. Jeremy Oldham
-
Hello, I am using Microsoft data provider for oracle. This is connecting to a Oracle 9i database. I would like to store and retrieve Japanese character using the Oracle client class. I have a problem right here. When i map .NET string datatype to the Varchar type of oracle client class, japanese character goes as junk characters(question marks). When i use Oracle Data Provider for .NET i had a datatype called Varchar2, where it working fine. Any one faced this problem thanks for your answer Cheers, Venkatraman Kalyanam Chennai - India "Being Excellent is not a skill, it is an attitude"
For storing Japanese characters you need to use Unicode/UTF-8 as a single character may require more than one byte. I am not sure about Oracle, but in SQL Server you will need to Nvarchar to store such data. Deepak Khajuria
-
Ensure that the page is set for Unicode encoding. I had trouble with this in SQL Server. I could input Russian characters through Query Analyzer and they would store correctly in the database, but when I entered the information through my web form, nothing but question marks. I change the page encoding to UTF-8 and all was well. Jeremy Oldham
I am using shift_JIS encoding. Cheers, Venkatraman Kalyanam Chennai - India "Being Excellent is not a skill, it is an attitude"