Make sure the stored procedure object exists in your database, ie that
was was run on the database.
A simple way is to use Enterprise Manager for SQL Server 2000.
Browse to your database.
Expand the database. You will see a container called Store
Procedures.
Expand stored procedures.
Browse for the name of the stored procedure.
[The command objects string will tell you what the stored procedure is
named. This comes after the EXEC or EXECUTE portion of the command
string.]
Or you can open Query Analyzer and attempt to execute the stored
procedure:
EXEC <storedprocedurename>
If it returns :
Could not find stored procedure 'xxx'.
Then you need to run your stored procedures on your database. Then
try your application again.
I don't remember exactly but I think that in some cases, restoring a
database may not restore all of the user objects, just tables/data.
This may only apply to replication. You may want to look in to that.
Marnee
On May 28, 2:42 pm, Henning Winkler <Henning.Wink...@t-online.de>
[quoted text, click to view] wrote:
> Hi all,
>
> I have a problem with a database on sqlserver 2000 ( 120 days eval ed)
> on Windows 2000.
> My database had been appended from another sqlserver 2000. But now I
> have problems to call a stored procedure.
> This sp is called by a VB6 application.
> First a command object ist created, a active connection and the
> command-type ist set. Then three parameters are set by parameters(1)
> = ...., parameters(2) = .... and parameters(3) = .... If the program
> calls the execute-method of the command object, an error occurs
> "stored procedure .....not found. In the sql server enterprise manager
> I can see the stored procedure, the owner its the same, that opens the
> connection via the vb application.
> On the other sqlserver this program works fine with the same db so i
> assume, the problem ist the appended database. (???)
> Any idea for a solution.
>
> Thanks
>
> Henning
[