I'll stand by my question: why GENERATE multiple result sets if you are not going to return them to the client? Why make SQL Server do all the work and eat all the clock cycles and generate all the I/O if you're not going to use the results?

-Mike

>Question 1 Explanation:
>I am not a VB programmer, but the programmers here say that they get errors if there is more than one result set and they only expect a single result set. They don't want to use the ADO commands that allow for multiple result sets.