# BUG: RETURN Statement After an RPC Causes Extra Result Set

Last reviewed: April 29, 1997
Article ID: Q114526

###

The information in this article applies to:

      - Microsoft SQL Server version 4.2 for OS/2

BUG#: OS/2: 1724 (4.2)

## SYMPTOMS

An extra result set is returned from SQL Server when a stored procedure containing a remote procedure call followed by a RETURN statement is executed. This does not happen if there is no RETURN statement following the EXECUTE statement or if a local procedure is executed instead of a remote one.

For example, if you execute the following stored procedure, you will see the problem:

       create proc rpcproc as
       execute <remote machine>...sp_who
       return
       go
       execute rpcproc
       go

## WORKAROUND

Modify the stored procedure, if possible, to avoid the explicit return statement following the call to execute the remote procedure. Another workaround is to make sure your front-end application is handling the extra result set properly. One recommend way of doing this is to execute the call to dbresults in a WHILE loop until it returns NO_MORE_RESULTS.

## STATUS

Microsoft has confirmed this to be a problem in SQL Server version 4.2 for OS/2. This problem does not occur in version 6.0.

> Additional query words: RPC dbresults DB-Library dblib
> Keywords : kbbug4.20 kbprg SSrvDB_Lib SSrvProg
> Version : 4.2
> Platform : OS/2
> THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 29, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.