I have a stored proc which returns multiple result sets. The results are consumed by a VBA client using ADODB to cycle through the result sets using the NextRecordSet method.
Among the genuine result sets it returns from SELECT statements, there is another result set from an INSERT INTO which the ADODB code skips past, as it's not openable as a RecordSet and does not contain anything useful anyway. I have had to add another INSERT INTO, which means changing all the code that uses this to skip another useless RecordSet.
Can anyone tell me if there's a way to suppress these result sets from INSERTs and UPDATEs? I have done quite a bit of googling but can't find anything about this.
I don't particularly like the way the SP works, but changing the fundamentals is not really an option as a lot of code depends on the current output.