Dumb Question - Prevent Deletion in Microsoft Access


	Back to Prevent Deletion Comments List

Upload Images Link Email

Dumb Question

Sandra Truax

2 years ago

I've played with this in test, but...

The member video shows how to use dLookup to see if there are any records in the child tables, and if so, delete them.

My question is, is it necessary to look first, or can the delete query just be ran for each child table, or could this possibly cause problems if there is no records in one of the tables? I know in testing, nothing happened, but before I use it as common practice, I wanted to check with y'all to see if there could possibly be problems down the line.

Scott Axton

2 years ago

I think you might have answered your own question.
If you run your delete for something that isn't there what response did you get?

If you say "Delete from xxxChildTable any records that match 123 ID"
Access is just going to do it. (Unless you have an Are you Sure in place.) It shouldn't throw an error if there aren't any.
The flip side is -- it is just going to delete records with out throwing an error.

Deleting records can have unintended consequences in either case. I really don't like doing it but some times you just cant get away from it. As long as you are practicing good self-preservation methods (BACK UPS) so you can recover from disaster if you need to.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Prevent Deletion.