Re: Stored procedure returning multiple recordsets
- From: Ahti Legonkov <leg0@xxxxxx>
- Date: Mon, 23 Oct 2006 16:11:13 +0300
Bob Barrows [MVP] wrote:
....
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.
Thanks! That's a useful tip.
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.
Actually I am using classic ADO (msado15.dll), I guess I should have mentioned that. I just used VB.NET to write the example as it would have been a bit longer when written in C++ and would contain too much details not related to problem.
I also found a another cure for my problem - Recordset has a member function called NextRecordset.
--
Ahti Legonkov
.
- Follow-Ups:
- Re: Stored procedure returning multiple recordsets
- From: Bob Barrows [MVP]
- Re: Stored procedure returning multiple recordsets
- References:
- Stored procedure returning multiple recordsets
- From: Ahti Legonkov
- Re: Stored procedure returning multiple recordsets
- From: Bob Barrows [MVP]
- Stored procedure returning multiple recordsets
- Prev by Date: Re: Stored procedure returning multiple recordsets
- Next by Date: Re: Stored procedure returning multiple recordsets
- Previous by thread: Re: Stored procedure returning multiple recordsets
- Next by thread: Re: Stored procedure returning multiple recordsets
- Index(es):
Relevant Pages
|
|