Catch... try block

[JJ297]

If I enter a new topic I don't get your topic was submitted...

If I enter in a duplicate I do get teh duplicate error message. What
am I doing wrong?


Catch ex As Data.SqlClient.SqlException
'Throw New ApplicationException("An error occurred while
trying to insert the record")
If TopicTxt.Text = "" Then
Lbloutcome.Text = "Your topic was submitted into the
database."
Else
Lbloutcome1.Text = "Duplicate entry topic already in
database, topic was not submitted"
End If

 

[sloan]

The code inside
Catch ex As Data.SqlClient.SqlException

is only going to run .. is something blows up.

.........

I would go through this blog:
http://blogs.msdn.com/kcwalina/archive/2005/03/16/396787.aspx

and rework the code.

 

[jx.su.go]

The code inside
Catch ex As Data.SqlClient.SqlException

is only going to run .. is something blows up.

........

I would go through this blog:http://blogs.msdn.com/kcwalina/archive/2005/03/16/396787.aspx

and rework the code.








- Show quoted text -

the catch will harm the performance.
judge the text of Lbloutcome before insert this data to database.

 

[Cowboy \(Gregory A. Beamer\)]

First, I would design it so you do not have to "blow up" with a duplicate
insert. I would, instead, use ExecuteNonQuery on a stored procedure and
return 0 if there is already a record. In this way, you can return an
"error" message without actually throwing an exception (which is expensive).

As for why you are not getting the success message, the answer is simple:
You are succeeding. Catch only works when you have an error. Since the data
entered the database without problem, there was no error, and there is no
message.

I would redesign for success (the rule) rather than failure (the exception).

 

[JJ297]

First, I would design it so you do not have to "blow up" with a duplicate
insert. I would, instead, use ExecuteNonQuery on a stored procedure and
return 0 if there is already a record. In this way, you can return an
"error" message without actually throwing an exception (which is expensive).

As for why you are not getting the success message, the answer is simple:
You are succeeding. Catch only works when you have an error. Since the data
entered the database without problem, there was no error, and there is no
message.

I would redesign for success (the rule) rather than failure (the exception).

--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA

*************************************************
| Think outside the box!
|







- Show quoted text -

Okay thanks!