Keyword Not Supported UNICODE in visual studio

NIK VYAVAHARE

11y3.7k.NET

Hello,i'm Using Visual Studio 10 and as a back end using oracle 9 i,when i do operations on data like insert,update,delete through web form i got the error that keyword UNICODE is not supported. Please suggest me and Thanks in Advance.

I have wriiten my conncetion string as like,

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

NIK VYAVAHARE10y ago
Sir,I have used as you suggested, nut its not worked,It shows new error like Keyword Not Supported:Provider,
So is there any solution?
Sourabh Somani10y ago
=msdaora;Data Source=CGS1DB15;User Id=cgs1db;Password=urPassword"/>

use this...
and if you are getting
“A network-related or instance-specific error occurred while establishing a connection to SQL Server…”

error
than read this article
7 things to check to resolve “A network-related or instance-specific error occurred while establishing a connection to SQL Server…”
NIK VYAVAHARE10y ago
But if i remove that UNICODE=TRUE it gives error like
A network-related or instance-specific error occurred while establishing a connection to SQL Server ...
so what exactly i have to do?
Please suggest me..
Banketeshvar Narayan10y ago
HI Nik,

The fact that .NET strings are unicode has nothing to do with connection string attributes. Look at your connection string, you probably have "unicode=true" in it, and Oracle's ODP doent have a connection string attribute called Unicode. Microsoft's data provider does. Oracle's doesnt. For a list of valid connect string attributes, check the [ODP docs|http://download.oracle.com/docs/pdf/E10927_01.pdf].

If Unicode is set to true when not using Oracle 9i client software to communicate with an Oracle 9i server, unpredictable results may occur.
Courtsey:
http://msdn2.microsoft.com/en-us/library/system.data.oracleclient.oracleconnection.connectionstring(VS.71).aspx
249

Keyword Not Supported UNICODE in visual studio

A network-related or instance-specific error occurred while establishing a connection to SQL Server ...