Oracle Provider Error

  • Thread starter Thread starter Bruce Whitehouse
  • Start date Start date
B

Bruce Whitehouse

Help!

I'm trying to execute an Oracle package (9i) from my VB.NET code using the
OracleProvider.

I get the following error...
System.Data.OracleClient.OracleException: ORA-01036: illegal variable
name/number

from the following code....
Dim objCommand As OracleCommand

Dim strPackage As String

boolReturn = True

strPackage = getPackageName(strTable) & ".PRC_DELETE"

objCommand = New OracleCommand(strPackage, objConnection)

objCommand.CommandType = CommandType.StoredProcedure

objCommand.Parameters.Add(New OracleParameter("@IN_TERMINAL_ID",
OracleType.Number))

objCommand.Parameters("@IN_TERMINAL_ID").Value = objTerminal.TerminalID

objCommand.Parameters.Add(New OracleParameter("@IN_DELETE_ALL",
OracleType.Number))

objCommand.Parameters("@IN_DELETE_ALL").Value = 1

Try

objConnection.Open()

boolReturn = objCommand.ExecuteNonQuery()

objConnection.close()

Catch e As Exception

boolReturn = False

strError = CStr(e.ToString())

End Try


Can anyone help?

Bruce
 
Help!

I'm trying to execute an Oracle package (9i) from my VB.NET code using the
OracleProvider.

I get the following error...
System.Data.OracleClient.OracleException: ORA-01036: illegal variable
name/number

from the following code....
Dim objCommand As OracleCommand

Dim strPackage As String

boolReturn = True

strPackage = getPackageName(strTable) & ".PRC_DELETE"

objCommand = New OracleCommand(strPackage, objConnection)

objCommand.CommandType = CommandType.StoredProcedure

objCommand.Parameters.Add(New OracleParameter("@IN_TERMINAL_ID",
OracleType.Number))

objCommand.Parameters("@IN_TERMINAL_ID").Value = objTerminal.TerminalID

objCommand.Parameters.Add(New OracleParameter("@IN_DELETE_ALL",
OracleType.Number))

objCommand.Parameters("@IN_DELETE_ALL").Value = 1
Click to expand...

I don't think these '@' should be in front of the parameter names
:)

FB
 
Frans

I worked this out (eventually) and have just come back to see if there were
any replies.

Yes, you're right - the @'s weren't needed. I think that must have been
some legacy code from my SQL Server days.

regards,
Bruce
 
Back
Top