Delete Child Table Entries

What I do is to set this up at the database level, which is foolproof. I use SQL Server. If you have your table relationships set up, you can specify what happens when the parent record is deleted or updated. For deletes, I choose "Cascade", which causes the dependent records in the child table to also be deleted at the same time the parent record gets deleted. The great thing about taking care of things like this at the DB level is that no matter where the delete occurs -- even in other apps/DB tools -- your referential integrity is always maintained.

This is exactly how I do it as well.

Thank you very much for your replies. I have 2 questions,
[list=2]
[]The two tables I posted are part of a bigger project where another table is involved, "Family." Family is the master table for Applicant (linked through FamilyID), and Applicant is the master table for Charges(Linked through ApplicantID). If I set the foreign key in the Applicant table as FamilyID and the foreign key in the Charges table as ApplicantID and add ON DELETE CASCADE on both tables; deleting a Family entry would also delete every Applicant that's a member of that family as well as all their charges, correct?
[]I already have "Before record updated" and "After record updated" events that I thought only ran for the specific entry being updated. After running the code above it seems like its updating the whole database, is that the case? See sample code below.

[/list]

• The two tables I posted are part of a bigger project where another table is involved, "Family." Family is the master table for Applicant (linked through FamilyID), and Applicant is the master table for Charges(Linked through ApplicantID). If I set the foreign key in the Applicant table as FamilyID and the foreign key in the Charges table as ApplicantID and add ON DELETE CASCADE on both tables; deleting a Family entry would also delete every Applicant that's a member of that family as well as all their charges, correct?

No. Each relationship has it's own rules for handling updates and deletes. If you add this rule to the relationship that links [Applicant] to [Charges], it should have no effect on any other relationships. The [Family] table would not be affected at all.

What I meant by it is that if Charges is linked to Applicant and Applicant is linked to Family. If I delete a Family, all the Applicants linked to that family would be deleted automatically and because some Charges are linked to those applicants these would also be deleted. Am I correct in this assumption? I apologize, I've never worked with ON DELETE CASCADE before.
As far as my other question, does ASPRuner automatically know that I'm only trying to update the data for the entries that share the same FAMILYID and APPLICANTID as the entry on the working session?

After some testing I figured out that the code above updates the whole DB, that's a problem.
I know there's something like

If I made a change in the "Charges" table (child table), what's the syntax to also update the "Applicant" table (master table) only for that specific applicant?
This is what I have right now, but it doesn't work.

Try something like this on before deleted event of Applicant Table:

Thank you jadach.
I'm trying to use a similar code to update my Family and Applicant tables when a new Charge is added or updated. I added the following code to the "Before record updated" event but get the error in the picture below.
Edit: Wanted to add a description of what this code is doing when a new charge is added/updated,

1. It looks at the APLICANT_ID of the charge being added/updated
   
2. Searches for this applicant in the "Applicants" table
   
3. Adds all "Charges" that have this same "APPLICANT_ID" and updates "Subsidy" in "Applicants" with this value.
   

Something similar will be done for the "TOTAL" in the "Family" table but we would be adding all "Subsidy," from the "Applicant" table, with the same "FAMILY_ID."

And just fyi, I'm not just posting questions and waiting for answers. I'm actually looking at similar questions in the forum, reading the manual and trying different things. Unfortunately, my case it a bit different since it deals with multiple tables and addition of fields before the update... I'm not sure how much more difficult that makes it.
These are just a few of the threads I've been using as references:
http://asprunner.com/forums/topic/21533-set-default-value-based-on-logged-in-user/

http://asprunner.com/forums/topic/22809-assign-value-returned-by-stored-procedure-to-varible/

http://asprunner.com/forums/topic/23366-inline-addedit/

http://asprunner.com/forums/topic/23817-how-do-i-apply-this-to-one-record/

http://asprunner.com/forums/topic/23838-database-security-with-windows-authentication/

http://asprunner.com/forums/topic/24450-fk-values-in-email-message/
https://xlinesoft.com/asprunnerpro/docs62/before_record_updated.htm

https://xlinesoft.com/asprunnerpro/docs62/data_access_layer.htm

https://xlinesoft.com/asprunnerpro/docs62/update_multiple_tables.htm

https://xlinesoft.com/asprunnerpro/docs62/before_record_deleted.htm

Looks like an issue with SQL Query you trying to execute. Instead of executing it print this query on the web page to see what exactly went wrong:

https://xlinesoft.com/asprunnernet/docs/debugging_tips.htm

Thanks to everyone for your replies. I finally got it, further testing needed. At first I wrote the code in the "Before record updated" event but it was adding the values before the item was added/updated. So I thought, "well... I can just copy the code to the 'After record updated' event," no luck. I had to change data[""].ToString() to values[""].ToString(). Side question, whats the difference between "values" vs. "oldvalues?" Is "oldvalues" the value of the field before the update?
Thanks again.