I have an VB6 aplication which use system stored procedure "sp_procedure_params_rowset" via OLEDB to know the SP's parameters!
This works all good when running on new installation of SQL Server. The users that call the SP are members of Public Role.
I have installed the application at one existing server and I began to have an error because the recordset become empty!
After searching a lot I see that can be a problem with server role permissions (Public) so to try to have the same behavior I DENY EXECUTE TO PUBLIC and when I run the query manually I receive the empty recordset.
My doubt is, how can I discover why at the 2nd server I can't receive queries' results?
I allready see the Public Role permissions and I don't have any DENY to any object
Can you help me?