how to prompt user if they try to delte wrong valu

method · June 15th, 2005, 01:11 PM

How to prompt user if they try to delete a record from datagrid which
has relationship with other table? I created a editable datagrid and
want to inform user if they try to delete a record that has reletions with other tables. I be happy if some one help me how i can do this in asp.net .Thanks

http://i5.photobucket.com/albums/y18...7/19932c0e.jpg (db reletion ship)

Here is my delete code :

Code:

Private Sub DataGridMatch_DeleteCommand(ByVal source As Object, ByVal e As System.Web.UI.WebControls.DataGridCommandEventArgs) Handles DataGridPlayer.DeleteCommand
        Dim MyCommand As SqlCommand
        Dim DeleteCmd As String = "Delete From players Where playerno = " & e.Item.Cells(2).Text
        MyCommand = New SqlCommand(DeleteCmd, MyConnection)
        MyCommand.Connection.Open()
        MyCommand.ExecuteNonQuery()
        MyCommand.Connection.Close()
        DataGridPlayer.EditItemIndex = -1
        BindDataGridPlayer()


    End Sub

jbenson001 · June 15th, 2005, 03:27 PM

You have a few options. You can write a query to see if the ID exists in any other table and warn the user. Or you can let the delet run and trap the sql error. Or you can put cascading deltes in your DB and let the delete run.

method · June 16th, 2005, 08:23 AM

Quote:

quote:Originally posted by jbenson001
You have a few options. You can write a query to see if the ID exists in any other table and warn the user. Or you can let the delet run and trap the sql error. Or you can put cascading deltes in your DB and let the delete run.

Thank u for u reply. well i do not want to vilote the db reletionship so i do not want to user cascade delete. How i can trap sql error. i be happy if u show me how.Thanks

jbenson001 · June 16th, 2005, 08:53 AM

Use the Try...Catch..End Try statement.

See the help in VS.

planoie · June 17th, 2005, 08:32 AM

Quote:

quote:Originally posted by method
well i do not want to vilote the db reletionship so i do not want to user cascade delete.

Method, I think you missed the point of cascade deletes. If you build tables that are related but do not place foreign keys on them you run the risk of deleting parent rows and leaving orphaned child rows. So you add on foreign keys. Of course, now you have relationship integrity. If you want to delete parent rows you must delete the child rows first in order to avoid violation of the relationship.

The whole intent for cascading deletes is to allow you to support referential integrity thru foreign key relationships but allow you to delete parent rows without having to worry about first deleting the child rows. The cascade delete does this for you.

You have to ask yourself the question: "Is it acceptable for a user to delete something that has dependant information that will also be deleted?"

There are often cases where the answer is NO because you need to maintain some history of information (ex. Product Orders). Then you have to design your database to support additional conditions on the tables such as adding an "Active" field to a "Products" table to indicate that the product is or is not active any more. That way your application can see the row still exists but we shouldn't include it in lists of active products. In this case, you would not want cascade delete on the foreign key to the Products table because you want the database to error out if you DID try to delete a product that had order history.

So in the end you are back to the suggestion Jim made which is to
A) Query the database and see if circumstances prevent a valid delete
B) Try the delete and catch the Sql exception

-Peter