Is there any way of handling error on establishing connection to SQL Server on application level?

That's the most practical way, I think. Sometimes you'll need to display different error message or different approach even though they have the same exception.

That's the most practical way, I think. Sometimes you'll need to display different error message or different approach even though they have the same exception. You can also try this article 4guysfromrolla.com/articles/081209-1.aspx but note that redirection is sometimes not a good option to say that something went wrong in your website especially in a page where user will fill-out a form, you don't want him to lose his progress, do you?

If you are using SqlDataSource forums.asp.net/t/978920.aspx/1.

Or you can read this article: 4guysfromrolla. Com/articles/081209-1. Aspx – domanokz Jun 28 at 6:13 I'm also thinking of exceptions from SqlDataSource.

I extensively use SqlDataSource on GridViews and DateilViews, if I'll also code exception handling everytime I use SqlDataSource, that would be too frustrating. – kaz Jun 28 at 6:18 See this article: forums.asp. Net/t/978920.

Aspx/1 They show here how to catch exception of SqlDataSource – domanokz Jun 28 at 6:24.

If you need to handle your errors on a single block, the best place is the global. Asax Application_Error method. There you can check the exception through: Exception ex = Server.GetLastError().

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.