Thread Subject: Adventures with RUNSTOREDPROCEDURE

I am puzzled by behavior of RUNSTOREDPROCEDURE, which
errors out on an operation that EXEC handles without
complaint.

I have a (toy) SQL Server 2005 stored procedure that
inputs a number and saves a subset of a table's rows to
another table.

create procedure dbo.temp_dimitri_testsp @maxvalue float
as
  select *
  into dbo.temp_dimitri_test4
  from dbo.temp_dimitri_test
  where value < @maxvalue;

No output is retrieved - yet

x = runstoredprocedure(conn,'dbo.temp_dimitri_testsp',
{71});
??? Error using ==> database.runstoredprocedure at 80
Procedure may return resultset. Use EXEC and FETCH

However,

curs = exec(conn,'execute dbo.temp_dimitri_testsp 71')

works, i.e. a table is created.

Can anyone explain this?

Thank you.

Problem solved: it looks like RUNSTOREDPROCEDURE does not
let one omit inputs - as

x = runstoredprocedure(conn,'dbo.temp_dimitri_testsp',{71},
{})

works.

Problem solved: it looks like RUNSTOREDPROCEDURE does not
let one omit inputs - as

x = runstoredprocedure(conn,'dbo.temp_dimitri_testsp',{71},
{})

works.