Cannot find Oracle data client

[bclegg]

Hi,
I am running Dot Net 7.1.3088 on top of framework 1.1.4322
I cannot find the system.data.oracleclient namespace.
I tried running the 'Managed Provider for Oracle ' oracle_net.msi.
This ran OK but still no client namespace.
Any ideas?
thanks
Bob

 

[Kevin Yu [MSFT]]

Hi Bob,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you could not find the
System.Data.OracleClient namespace in VS.NET. If there is any
misunderstanding, please feel free to let me know.

When a project is created, a reference to the assembly
System.Data.OracleClient.dll is not added by default. If you need to use
classes under that namespace, you have to add reference to the assembly.
Here are the steps:

1. Select Project / Add Reference... from the main menu.
2. In .NET tab, find System.Data.OracleClient.dll and double click on it.
3. Click OK to add reference to it.

When done, we can use classes under namespace System.Data.OralcleClient in
our project.

HTH. If anything is unclear, please feel free to reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[Bob Clegg]

Hi Kevin,
Spot On.
I was assuming that it would appear in the System.data collection by
default.
Thanks
Bob.

 

[Kevin Yu [MSFT]]

Hi Bob,

It was nice to hear that the problem is resolved. Thanks for sharing your
experience with all the people here. If you have any questions, please feel
free to post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[bclegg]

Hi Bob,

It was nice to hear that the problem is resolved. Thanks for sharing your
experience with all the people here. If you have any questions, please feel
free to post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Hi Kevin,
One slight correction is needed on my post.
It turns out that if you are using an SQLServer Client command of
commandtype=text then any parameter name can be used.
ie The command string is "exec proc_SetWidget @Myparam1,MyParam2"

If you specify commandtype =Storedprocedure and use the command string of
"proc_SetWidget" then your parameter names must match what is in the
stored procedure.
I had been using SQlServer client the first way.
When I went to use Oracle client the examples were done the second way.
regards
Bob

 

[Kevin Yu [MSFT]]

Hi Bob,

As far as I know, we have to give names to parameters according to the
command text both in SQL client or in Oracle client. Because in .NET
provider, the SQL command maps parameter objects according to their names,
not orders.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

 

[bclegg]

Hi Kevin,
hmmm,
Well, I can only give the following as an example:


Top few lines of proc. Note @id.

CREATE PROCEDURE proc_WriteProfileUpdate
@id int,
@description varchar(50)=null,
etc etc ...


Calling code using command type of text. (Works)
strSQL = " Exec proc_WriteProfileUpdate @profile_id,@description, etc
etc ..."

Calling code using command type of StoredProcedure. (fails with
"@profile_id is not a parameter for proc_WriteProfileUpdate")
strSQL = "proc_WriteProfileUpdate"

I will probably move the SQl client command types over to
StoredProcedure and alter the parameter names, seeing that is the way it
is intended to work.
regards
Bob

 

[Kevin Yu [MSFT]]

Hi Bob,

We have to name parameters according to the names used in stored procedures
in ADO.NET. So this can resolve the problem. Thanks for sharing your
experience with all the people here. If you have any questions, please feel
free to post them in the community.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."