catch sql exception

[gerry]

My 1st crack at doing things the RAD way - I have a web form with a
SqlDataSource and a DetailsView.
I am trying to find a way to catch database exceptions so that i can display
an appropriate error message and let the user fix the data and resubmit the
form. ( In this case it is a dup key violation - so nothing I can pre-edit
for )

The only way I can see to catch db exceptions is by overriding Page.OnError
and looking at Context.Error. This gives me access to the exception and
Context.ClearError() stops the default error handling but by this point the
response has been cleared and so returns an empty page to the browser.
I am surprised that there isn't an OnError associated with either the
SqlDataSource or the DetailsView.

It almost looks like I am going to be forced to scrap the SqlDataSource and
go back to manual databinding etc in order to be able to catch db
exceptions.

I haven't found any references to this in google - so I assume that I am
missing something obvious.

Gerry

[geekboy0001]

Wrap the SQL call within a TRY-CATCH. ie:
Try
DataConnection.Open
DataReader.Open -- some sql call
DataReader.Read or whatever
The sql call will fail here
Catch ex as exception
Do your error handling here. your error is ex.message
Make sure to close your reader and your connection here too
End Try

[gerry]

Hey geek ,

well that is exactly the problem., when using an SqlDataSource none of this
code exists, all db interaction is handled by the SqlDataSource object
behind the scenes.
the whole point in trying this approach was to get away from all the hand
coding.
and it does work very well as long as you don't run into any db exceptions.

Gerry
<ge*********@yahoo.comwrote in message
news:11**********************@p79g2000cwp.googlegr oups.com...

Wrap the SQL call within a TRY-CATCH. ie:
Try
DataConnection.Open
DataReader.Open -- some sql call
DataReader.Read or whatever
The sql call will fail here
Catch ex as exception
Do your error handling here. your error is ex.message
Make sure to close your reader and your connection here too
End Try

[Mark Rae]

"gerry" <ge**@nospam.nospamwrote in message
news:OE**************@TK2MSFTNGP05.phx.gbl...

and it does work very well as long as you don't run into any db
exceptions.

Have you tried:

Catch ex as SqlException

[gerry]

tried it where ?
all of the db update code is hidden away in the SqlDataSource object and
there is no place to use a try/catch.
"Mark Rae" <ma**@markN-O-S-P-A-M.co.ukwrote in message
news:OS**************@TK2MSFTNGP04.phx.gbl...

"gerry" <ge**@nospam.nospamwrote in message
news:OE**************@TK2MSFTNGP05.phx.gbl...

and it does work very well as long as you don't run into any db
exceptions.

Have you tried:

Catch ex as SqlException

[gerry]

i did get this working , but its pretty kludgy

in OnError, I save my error message in the session, i do a Server.Transfer
back to the same page with form preservation. in Page_Load I look for the
message in the session, if its there I display it, remove it from the
session and cancel any further processing / updates.

I still have to wonder why there is no OnError associated with the
SqlDataSource object.

Gerry

"gerry" <ge**@nospam.nospamwrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...

My 1st crack at doing things the RAD way - I have a web form with a
SqlDataSource and a DetailsView.
I am trying to find a way to catch database exceptions so that i can

display

an appropriate error message and let the user fix the data and resubmit

the

form. ( In this case it is a dup key violation - so nothing I can pre-edit
for )

The only way I can see to catch db exceptions is by overriding

Page.OnError

and looking at Context.Error. This gives me access to the exception and
Context.ClearError() stops the default error handling but by this point

the

response has been cleared and so returns an empty page to the browser.
I am surprised that there isn't an OnError associated with either the
SqlDataSource or the DetailsView.

It almost looks like I am going to be forced to scrap the SqlDataSource

and

go back to manual databinding etc in order to be able to catch db
exceptions.

I haven't found any references to this in google - so I assume that I am
missing something obvious.

Gerry

[brians[MCSD]]

Hello Gerry,

You should be able to add a handler for the relevant event: selected,
updated, inserted, deleted. Then, in the handler look at the
SqlDataSourceStatusEventArgs property Exception. If it's not null then an
exception has occurred. For example if the selected command threw an
exception:

protected void SqlDataSource1_Selected(object sender,
SqlDataSourceStatusEventArgs e)
{
if (e.Exception != null)
{
// handle the exception
}
}
--
enjoy - brians
http://www.limbertech.com
"gerry" wrote:

My 1st crack at doing things the RAD way - I have a web form with a
SqlDataSource and a DetailsView.
I am trying to find a way to catch database exceptions so that i can display
an appropriate error message and let the user fix the data and resubmit the
form. ( In this case it is a dup key violation - so nothing I can pre-edit
for )

The only way I can see to catch db exceptions is by overriding Page.OnError
and looking at Context.Error. This gives me access to the exception and
Context.ClearError() stops the default error handling but by this point the
response has been cleared and so returns an empty page to the browser.
I am surprised that there isn't an OnError associated with either the
SqlDataSource or the DetailsView.

It almost looks like I am going to be forced to scrap the SqlDataSource and
go back to manual databinding etc in order to be able to catch db
exceptions.

I haven't found any references to this in google - so I assume that I am
missing something obvious.

Gerry

[gerry]

Thanks Brian , that did it.
"brians[MCSD]" <br********@discussions.microsoft.comwrote in message
news:ED**********************************@microsof t.com...

Hello Gerry,

You should be able to add a handler for the relevant event: selected,
updated, inserted, deleted. Then, in the handler look at the
SqlDataSourceStatusEventArgs property Exception. If it's not null then an
exception has occurred. For example if the selected command threw an
exception:

protected void SqlDataSource1_Selected(object sender,
SqlDataSourceStatusEventArgs e)
{
if (e.Exception != null)
{
// handle the exception
}
}
--
enjoy - brians
http://www.limbertech.com
"gerry" wrote:

My 1st crack at doing things the RAD way - I have a web form with a
SqlDataSource and a DetailsView.
I am trying to find a way to catch database exceptions so that i can

display

an appropriate error message and let the user fix the data and resubmit

the

form. ( In this case it is a dup key violation - so nothing I can

pre-edit

for )

The only way I can see to catch db exceptions is by overriding

Page.OnError

and looking at Context.Error. This gives me access to the exception and
Context.ClearError() stops the default error handling but by this point

the

response has been cleared and so returns an empty page to the browser.
I am surprised that there isn't an OnError associated with either the
SqlDataSource or the DetailsView.

It almost looks like I am going to be forced to scrap the SqlDataSource

and

go back to manual databinding etc in order to be able to catch db
exceptions.

I haven't found any references to this in google - so I assume that I am
missing something obvious.

Gerry