>I'll usually do that when I >don't< want to display an error to the user. The fact that an error occurred isn't something they should/need to know about. Here's some code from a webpage I've got (the "catch" isn't completely empty, but it easily could have been if I moved some code around):
>
>

>// Grab the querystring "cat" and use it to retrieve
>// the category list.
>// In case of an exception, catch any funky variables
>// and just reset the Category key to 0
>try
>{
>	iCategory = int.Parse(Request.QueryString["cat"]);
>}
>	catch (System.Exception ex)
>{
>	iCategory = 0;
>}
>

>
>The idea behind the code is that if the "cat" querystring variable was changed to something that int.Parse() would choke on (eg. throw an exception), then I reset to a default value. For example, if someone was curious about what would happen if they modified the URL from something like http://www.mywebsite.com/MyPage.ASPX?cat=1 to http://www.mywebsite.com/MyPage.ASPX?cat=ABC, my code won't display any nasty error messages.

This is a great example of where to you Try/Catch. Thank you very much.