We are trying to use named parameters to execute stored procedures but regardless of what we construct, they seem to be ignored and the order of the parameters is observed instead.
As an example below, the iclientid is the 32nd parameter but we are only passing in 5 parameters, so iclientid is going into the 5th parameter which happens to be Add1, obviously not what we want.
Are we doing something wrong, any help most appreciated!
asked 15 Mar '16, 06:14
Hi, to follow on from what Jeavon said..
We pass those parameters to the following method which executes a stored procedure
It seems to ignore the name of the parameters and just put them in the order provided. We are updating a record and only really want to provide the parameters to update and not the whole range.
I've removed the '@' symbols as suggested above and changed our connection string so that it is in the following format (after a bit of digging in the docs)
This is connecting fine. Will this make it use the ADO.NET provider rather than go through the OLE DB? Or is there another step to it?
answered 16 Mar '16, 14:07
Thanks for your help here. The web guys are off to do some changes and try to make calls directly without using the steps of the embedded processes. Hopefully that will solve the problem.
Have a great Easter.
answered 24 Mar '16, 07:32