I'm trying to figure out what is the best method of communicating a error back to an ADO provider. My initial reaction was to use RAISEERROR, but it is my understanding that ADO doesn't make it easy to retrieve the specific error message raised by the SQL Server.
I also considered using a Return value but it sounds to me that I'd be just getting one more recordset and while I could just do .NextRecordset, it sounds too much for what should be a quick peek to verify that the operation suceeded.
So, what would be considered the most simplest way to inform the client via ADO that the operation was aborted by the SP (due to excessive number of records)?
I also considered using a Return value but it sounds to me that I'd be just getting one more recordset and while I could just do .NextRecordset, it sounds too much for what should be a quick peek to verify that the operation suceeded.
So, what would be considered the most simplest way to inform the client via ADO that the operation was aborted by the SP (due to excessive number of records)?