Re: Stored procedure returning multiple recordsets
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Mon, 23 Oct 2006 08:27:44 -0400
Ahti Legonkov wrote:
Hello!
I have a stored procedure like this (it's the shortest I could come
up with to demonstrate the behaviour. the select gets data from a
table and returns several rows):
create proc p3
as
insert into table3(blah) values('12345')
select @@identity
The same answer applies to both classic ADO and to ADO.Net:
Add "SET NOCOUNT ON" to the procedure to suppress the informational "x
rows effected" message generated by the insert statement and returned to
the client as a closed resultset.
and VB.NET code to use it:
There was no way for you to know it (except maybe by browsing through
some of the previous questions in this newsgroup before posting yours -
always a recommended practice) , but this is a classic ADO newsgroup.
ADO.Net bears very little resemblance to classic ADO so, while you may
be lucky enough to
find a dotnet-knowledgeable person here who can answer your question,
you can eliminate the luck factor by posting your question to a group
where those dotnet-knowledgeable people hang out. I suggest
microsoft.public.dotnet.framework.adonet.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- Follow-Ups:
- Re: Stored procedure returning multiple recordsets
- From: Ahti Legonkov
- Re: Stored procedure returning multiple recordsets
- References:
- Stored procedure returning multiple recordsets
- From: Ahti Legonkov
- Stored procedure returning multiple recordsets
- Prev by Date: Stored procedure returning multiple recordsets
- Next by Date: Re: Stored procedure returning multiple recordsets
- Previous by thread: Stored procedure returning multiple recordsets
- Next by thread: Re: Stored procedure returning multiple recordsets
- Index(es):
Relevant Pages
|
|
