>>I am wondering about how practical is to use Try/Catch/Finally error handling.
>>
>>You cannot get Server.GetLastError() in Catch block, therefore, making an informative error message is difficult. If you don't have Try/Catch, the global error page (from global.asax) will show an error message anyway.
>>
>>Where do you find Try/Catch/Finally practical to implement where the error message is informative?
>
>You pass the exception to the catch.
>Catch (Exception e)
>{
> e.Message
>}
In the couple of examples I ran, the e.Message does not really point to to the cause of the problem.
For example, when failing to create a connection object to VfpOleDb the error message is "One or more accessor flags were invalid".
Do you find, in your work, that e.Message provides information user can use?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
