Re: Command Object Output Parameter Undefined?
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Fri, 6 Oct 2006 06:39:10 -0400
Ross McKay wrote:
On Thu, 5 Oct 2006 10:11:03 -0400, "Bob Barrows [MVP]" wrote:
[...]
My SOP is to use GetRows to stuff the data from the recordset into an
array, close the recordset, then retrieve the output and return
parameter values, allowing me to immediately close the connection
before starting to process the data.
An alternative is to use client-side cursors in ADO. This is
particularly useful if you use a single stored proc call to return
parameters and multiple recordsets. No messing with arrays.
I did say that, but in ASP (which I suspect the OP is using due to his use
of Response.Write), it's best to get in and get out of the database quickly,
a goal which is facilitated by using GetRows. Admittedly, using disconnected
recordsets can accomplish the same goal, but these are usually overkill in
ASP, where all one usually needs to do is grab a set of records and
transform them to html, using SQL DML statements to perform updates instead
of expensive cursors.
--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"
.
- References:
- Command Object Output Parameter Undefined?
- From: gary.huntress@xxxxxxxxx
- Re: Command Object Output Parameter Undefined?
- From: Bob Barrows [MVP]
- Re: Command Object Output Parameter Undefined?
- From: Ross McKay
- Command Object Output Parameter Undefined?
- Prev by Date: Re: Command Object Output Parameter Undefined?
- Next by Date: Re: MS Office Update to Access 2003 killing me?
- Previous by thread: Re: Command Object Output Parameter Undefined?
- Next by thread: Re: MS Office Update to Access 2003 killing me?
- Index(es):
Relevant Pages
|
|