Re: 'The stored procedure executed successfully but did not return any records'

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

You must use global temporary tables, with two #, not local temporary
tables. See http://support.microsoft.com/kb/q232379/ for exemple. Of
course, this could lead to serious problem if you don't take some
precautions in a multi-users environment.

Make sure that you have a proper use of the SET NOCOUNT ON statement. If
your query is returning multiple recordset, you can also access each of them
with the .NextRecordset method of the Recordset object.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC


"Matt Smith" <someone@xxxxxxxx> wrote in message
news:OjfgOxMTFHA.584@xxxxxxxxxxxxxxxxxxxxxxx
>I am trying to use a stored procedure within an access .ADP that first
> creates a temporary table and then uses it in conjunction with other
> tables
> to generate a record set. When I run this through Query Analyzer this
> seems
> to generate a single rowset, however when I run in through the .ADP it
> generates the message:
>
> 'The stored procedure executed successfully but did not return any
> records'
>
> If I add another query at the start of the stored procedure, the .ADP will
> return the rowset for it, but not the final one, leading me to believe
> that
> the reason the original sp did not work is that the ADP is trying to use a
> rowset for the query that actually creates the temporary table. Is there
> any way that I can either specify that there should be no rowset returned
> for the table creating SELECT statement, or is there some way to get the
> .ADP to return the final rowset?
>
>
>
>


.

Relevant Pages