<div>
Hi,<br />
<br />
Use Try/Catch expression to do so.<br />
<br />
For instance,<br />
<br />
Try<br />
Your operations here (insert or delete or update or select<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; Catch ex As Exception<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 'If error, notify the user<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Label1.Text = ex.Message<br />
<br />
&nbsp; &nbsp; &nbsp; &nbsp; End Try<br />
&nbsp; &nbsp; &nbsp; &nbsp; Conn.Close()<br />
<br />
The part you are looking for is the ex.Message<br />
<br />
Whatever message your stored proc displays when an error occurs, is transmitted using ex.Message.<br />
<br />
To get that to work though, have a label on your markup.<br />
<br />
In my case, label is called label1
</div>


<div>
I actually do that right now. The reason I asked is because I performed a INSERT transaction and the action timed out. That's the first time that's ever happened. The error message returned in the &quot;Catch&quot; portion was that the action &quot;timed out&quot;...which is very vague. I need more information in order to debug the issue. I eventually figured it out that it was the Stored Procedure. But I want my VB.Net to catch any errors that are thrown in the SP.
</div>


<div>
Ok, I have a better understanding of your question now.<br />
<br />
You are right, in situations such as that, try/catch is usually vague.<br />
<br />
I usually do two things,<br />
<br />
1, add debug=&quot;true&quot; at top of the markup page.<br />
2, I comment out the try/catch.<br />
<br />
In the absence of these two instances, I am not sure vb.net is capable of catching errors not caused by your SP.<br />
<br />
And if it is your SP causing an error, it needs to be resolved on the backend first.<br />
<br />
I am pretty sure you know that anyway.<br />
<br />
You can log at log files and even viewer for any issues that could be causing the timeout issue.<br />
<br />
Code optimization could be looked at as well.<br />
<br />
Good luck.
</div>


<div>
Thanks James...I didn't realize all that was possible to trap with the Catch phrase.
</div>


<div>
<div class="content wysiwyg-content">
I want to check for errors from within my VB.Net app when I run a Stored Procedure. For example, if a database table was changed and that change wasn't reflected in a SP, it will throw an exception. How can I check for that in my VB.Net?<br />
<br />
Thanks!
</div>
</div>


I want to check for errors from within my VB.Net app when I run a Stored Procedure. For example, if a database table was changed and that change wasn't reflected in a SP, it will throw an exception. How can I check for that in my VB.Net?

Thanks!

Checking for Errors on a Stored Procedure from within a VB.Net app?

Visual Basic .NET (VB.NET) is an object-oriented programming language implemented on the .NET framework, but also supported on other platforms such as Mono and Silverlight. Microsoft launched VB.NET as the successor to the Visual Basic language. Though it is similar in syntax to  Visual Basic pre-2002, it is not the same technology,