Hi MickeyBob
Thanks for your reply.
Your first example as you also mention is not very good. You will end up with a single coloumn table with combined values which will be very hard to seperate.
I’m not sure if I can use the second suggestion because it doesen’t handle multiple recordset from the “nested” SP?
The called SP returns a single reulstset which is then just inserted into a temp table. But please correct me if i’m wrong.
The 3 example you refer to is talking about using a CLR function. And that is basically the setup I’m using at the moment where I use RSview’s VBA to call the stored procedure and then “browse” through the different recordsets and the varying rows of each recordset.
So I can’t se that I will gain much by using a CLR function on my database because I will just move my VBA from a client to the SQL server which doesent make the system more transparant.
I’m getting more and more convinced that I have to choose between to things.
A more transpatrant system where I need to change the already defined SP to make them more simple and return only a single resultset
Or keep the system as it is and live with the vba logic running on a client