BUG: RETURN Statement After an RPC Causes Extra Result Set

  - Microsoft SQL Server version 4.2 for OS/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.