VB6 and ADO problem in getting a recordset
- From: handshaper@xxxxxxxxx
- Date: 13 Dec 2006 15:27:53 -0800
Hello all,
I have an odd problem. I have a stored procedure that make use of
cursors to build dynamic sql for returning multiple recordsets in one
stored procedure call from VB6 (via ADO sql exec command).
VB is able to process each recordset until one particular recordset
(each is a result from different databases that we have on our SQL
Server). AT that particular recordset/database, a NextRecordSet
returns nothing, and VB assumes that there are no more recordsets after
that.
But therein lies the problem, there exists additional recordsets after
that particular recordset. Doing a "exec <name of stored procedure>"
returns everything that VB needs.
Does anybody have any idea why ADO/VB would consider that particular
recordset to be nothing/null and how I can fix that? It looks like to
be a data issue that is causing ADO to puke.
Todd
.
- Follow-Ups:
- Re: VB6 and ADO problem in getting a recordset
- From: Mark McGinty
- Re: VB6 and ADO problem in getting a recordset
- Prev by Date: Long SQL commands (>2k) with connection.execute
- Next by Date: SqlDataAdapter and timeout
- Previous by thread: Long SQL commands (>2k) with connection.execute
- Next by thread: Re: VB6 and ADO problem in getting a recordset
- Index(es):
Relevant Pages
|
