In this article, Garth discusses how to use access custom error messages generated by SQL Server with the Errors Collection of ADO. This is a follow up to the earlier Handling Errors in Stored Procedures article.
I can retrieve one error from ADODB.Connection.Errors collection but when I try to report multiple non fatal errors from a stored proc to an ADO connection/command, I can only retrieve the first one. For all the hemming and hawing various texts about ADO do regarding the Errors collection, and making sure to check for multiple errors, I would think this would work. Any ideas?
When I was in college all I wanted was to get out. Now that I'm out all I want to do is go back.
quote: Handling Custom Errors in client app Article <P>I followed it and it does not work!!!!!!! There is no description being sent back, only the nativeErrorCode.
Can someone help?
Cheers Ric
Hi Ric I also followed the article and my client application was visual basic. But I also had the same probleme as you. Could you already solve the problem?
Article: Handling Custom Errors in a Client Application
Posted - 02/25/2001 : 20:44:27
