ASP - Re: Strange behavior with SQL text field and ADO Parameter....a challenge for the exp

You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author

Re: Strange behavior with SQL text field and ADO Parameter....a challenge for the exp

Dan

2004-07-01, 8:55 pm

Tried it, but it still doesn't work (output parameter is 0 after execute
statement).

Also, remember it works fine if the 2nd parameter's length is < 8002.

Thanks,
Dan

"Bob Barrows [MVP]" <reb01501@NOyahoo.SPAMcom> wrote in message
news:OjLF2h7XEHA.2816@TK2MSFTNGP11.phx.gbl...
> The first thing I see is the lack of SET NOCOUNT ON in your stored
> procedure. Without that, your procedure is returning a resultset
containing
> an "x records affected by the insert statement" message.Ouput parameter
> values are not returned until resultsets are consumed. Add SET NOCOUNT ON
to
> prevent the creation of the resultset.
>
> Bob Barrows
>
>
> Dan wrote:
>
> --
> 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.
>
>

Sponsored Links