BorlandTalk.com

dbo.db · Guest

I've established a connection with a particular database on a server (via a UDL file). Interacting with that DB works as it should.

I now want to call a stored procedure on a *different* database, but it's on the *same* server.

It works fine via Query Analyzer. The stored proc is simply qualified by the DB name and the DBO prefix (AnotherDB.dbo.storedProc1).

But it does not work via TADOStoredProc. It complains that my parameters aren't valid. Specifically, it complains about the first paramter in the list (@vParam1 does not exist).

Just to see what would happen, I passed zero parameters (the stored procedure requires them). In that scenario, I get an exception complaining the procedure expects a parameter, the very same parameter Builder said didn't exist when it was passed.

What's going on? Or is calling another database which is on the same server simply not supported? Am I forced to open up another connection?

Guest

[Oops... didn't press enter. I'm new... and can't read
instructions apparently Razz

I've reposted it so it's easier to
read]

I've established a connection with a particular database on a
server (via a UDL file). Interacting with that DB works as it
should.

I now want to call a stored procedure on a *different* database,
but it's on the *same* server.

It works fine via Query Analyzer. The stored proc is simply
qualified by the DB name and the DBO prefix
(AnotherDB.dbo.storedProc1).

But it does not work via TADOStoredProc. It complains that my
parameters aren't valid. Specifically, it complains about the
first paramter in the list (@vParam1 does not exist).

Just to see what would happen, I passed zero parameters (the
stored procedure requires them). In that scenario, I get an
exception complaining the procedure expects a parameter, the very
same parameter Builder said didn't exist when it was passed.

What's going on? Or is calling another database which is on the
same server simply not supported? Am I forced to open up another
connection?