Re: Call stored proc from ADODB.Command
From: Al Reid (areidjr_at_reidDASHhome.com)
Date: 05/06/04
- Next message: alex: "Re: Call stored proc from ADODB.Command"
- Previous message: Gordon Swan: "Data Report Designer"
- In reply to: alex: "Call stored proc from ADODB.Command"
- Next in thread: alex: "Re: Call stored proc from ADODB.Command"
- Reply: alex: "Re: Call stored proc from ADODB.Command"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 6 May 2004 08:32:44 -0400
Post the exact DDL for the SP along with the code you are using to call it.
-- Al Reid "It ain't what you don't know that gets you into trouble. It's what you know for sure that just ain't so." --- Mark Twain "alex" <anonymous@discussions.microsoft.com> wrote in message news:4C4BDCF4-D7FF-48A9-875E-2B86F6A649C9@microsoft.com... > Dear all, > I have a stored proc on my SQL 2000 that looks something like: > ... > UPDATE ... SET ... > > ... > The problem is that when I call for that proc using ADODB.Command object, everything that is before UPDATE statement is executed, but everything, that's after - not. > I use standart syntax for calling: > Dim cmd as new adodb.command > with cmd > .activeconnection = de.cn > .commandtype = 4 > .commandtext = "my_sp" > .execute > end with > To test executing I inserted RAISERROR after UPDATE statement and it never works... > Executing that proc from query analyzer works fine. > > What is the possible reason of this behaviour? > alex
- Next message: alex: "Re: Call stored proc from ADODB.Command"
- Previous message: Gordon Swan: "Data Report Designer"
- In reply to: alex: "Call stored proc from ADODB.Command"
- Next in thread: alex: "Re: Call stored proc from ADODB.Command"
- Reply: alex: "Re: Call stored proc from ADODB.Command"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|