Re: SQLHelper output parameters problem
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Tue, 19 Dec 2006 14:32:14 -0500
darko wrote:
Hi,There was no way for you to know it (except maybe by browsing through
can anyone help me with the problem extracting output parameter from
Data Application Blocks, SQLHelper.ExecuteDataset command,
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.
However, the answer is likely to be the same for either technology:
the lack of a "SET NOCOUNT ON" statement in the stored procedure is
allowing the informational "x rows effected" messages to be passed to
the client. These messages are passed as resultsets which must be
consumed by the client before output and return values are returned to
the client.
--
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.
.
- Prev by Date: Re: prepared sql statements
- Next by Date: OleDbConnectionString Vista
- Previous by thread: prepared sql statements
- Next by thread: OleDbConnectionString Vista
- Index(es):
Relevant Pages
|
|
