"SQLException" or "Exception"

[vcllvc]

Should I catche a "SQLException" or an "Exception" while filling a dataset?

 

[NeilTrain]

if you catch SQLExceptions, any other type of exception will go unhandled. You really only need to handle the SQL excpetion if it has info you need that the exception doesn't (I havent had this problem since the Excpetion has always had all the info i needed to find the problem)

But if you want to get really fancy, you can catch BOTH types of exceptions. You do this by declaring two catch blocks, one with each exception type. When an error gets raised, the catch block with the appropriate exception will get fired, for example:

try
{
     // some sql code here...
}
catch(SqlException se)
{
     // Handle SQL Exception here...
     MessageBox.Show("SQL Exception occurred");
}
catch(Exception e)
{
     // Some non sql exception happened...
     MessageBox.Show("Unknown Exception occurred");
}

 

[chiph]

The MSDN documentation falls down here a little bit. They normally tell you what exceptions can possibly be thrown.

I traced it all the back to IDbCommand.ExecuteReader, and none of the intervening classes or methods say what exceptions they throw.

So, just do as NeilTrain suggests.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first