Re: Command Object Output Parameter Undefined?
- From: Ross McKay <rosko@xxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 06 Oct 2006 00:29:12 GMT
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.
--
Ross McKay, Toronto, NSW Australia
"Let the laddie play wi the knife - he'll learn"
- The Wee Book of Calvin
.
- Follow-Ups:
- Re: Command Object Output Parameter Undefined?
- From: Bob Barrows [MVP]
- Re: Command Object Output Parameter Undefined?
- References:
- Command Object Output Parameter Undefined?
- From: gary.huntress@xxxxxxxxx
- Re: Command Object Output Parameter Undefined?
- From: Bob Barrows [MVP]
- Command Object Output Parameter Undefined?
- Prev by Date: Re: Command Object Output Parameter Undefined?
- Next by Date: Re: Command Object Output Parameter Undefined?
- Previous by thread: Re: Command Object Output Parameter Undefined?
- Next by thread: Re: Command Object Output Parameter Undefined?
- Index(es):
Relevant Pages
|