G
Guest
I have posted a query before on this particular issue but no one had ever heard of this issue, and I find it difficult to swallow as well, but this is what is happening.
When a read an Oracle table and I have a column which has the exact same value in the first row and the second row, the second row part of the row has "garbage" after about 4 characters. So if the first record has the value of "Happy Birthday", the second row will show "Happ\0\0\0".
If I look at this same information using the same query and using Toad to execute my query, all is well both the first and the second record say "Happy Birthday".
This happens for each and every table that I read and it is repeatable without exception.
The column type that I am having problems with is "VarChar2". I am reading the column as follows: String myField = dr.GetString(3). I see there is a method of "GetOracleString(3)" and I have tried this method with the same results.
I am using the "System.Data.OracleClient" namespace, which is the Microsoft version of the drivers. I am accessing an Oracle 8I table (or atleast this is what I am told).
I am thinking of installing the Oracle version of the drivers or using the standard oledb drivers to get around the problem.
Can anyone point me in the right direction on this issue?
When a read an Oracle table and I have a column which has the exact same value in the first row and the second row, the second row part of the row has "garbage" after about 4 characters. So if the first record has the value of "Happy Birthday", the second row will show "Happ\0\0\0".
If I look at this same information using the same query and using Toad to execute my query, all is well both the first and the second record say "Happy Birthday".
This happens for each and every table that I read and it is repeatable without exception.
The column type that I am having problems with is "VarChar2". I am reading the column as follows: String myField = dr.GetString(3). I see there is a method of "GetOracleString(3)" and I have tried this method with the same results.
I am using the "System.Data.OracleClient" namespace, which is the Microsoft version of the drivers. I am accessing an Oracle 8I table (or atleast this is what I am told).
I am thinking of installing the Oracle version of the drivers or using the standard oledb drivers to get around the problem.
Can anyone point me in the right direction on this issue?