A little update.
So it seems that the issue is not related to the return values and recordset.
I have created a small test application which returns a recordset just fine.
Could it be possible that SQL 2005 prevents information from sysobject to be exported (using SQL)?
I have this in a stored procedure where I fetch a list of stored procedures where a user has rights:
...
User Profile
Collapse
-
return values and recordset in one stored procedure
Hi
We have an application that runs fine on SQL 2000. Due to other applications we are forced to move to SQL 2005.
One Stored Procedure isn't working on the new SQL 2005. It's a SP with output parameters and a recordset. It's working fine on SQL 2000.
The data is returned through OLEDB to a VB6 application. In this application the output parameters are working fine (can access them). But the recordset...
No activity results to display
Show More
Leave a comment: