Access 2010 Cascade Delete isn't there...

[chuckcoleman]

I have a split database. I've gone into the backend database and created a relationship between two tables Enforcing Referential Integrity. I also checked Cascade Update Related Fields and Cascade Delete Related Records. Saved it and didn't get any errors. The relationship type was One-to-Many. When I go to the frontend datbase and look at relationships there, Enforce Referential Integrity is checked BUT neither the Cascade Update or Cascade Delete are checked. (All three are grayed out but that's understandable; Access wants those edited in the backend).

What's going on? I need the Cascade Delete to function.

 

[gemma-the-husky]

don't know about Access 2010 - but I never ever use cascading anything. I think its unhelpful and dangerous.

much better to control it, if its needed, then let it happen uncontrolled

 

[Galaxiom]

It is useful for the front end to be aware of the referential integrity to derail attempts to add records to the related table without master records. However the front end cannot impliment the cascades itself so the options are copmletely irrelevent there.

As Dave says, some developers shun the use of cascades for fear that they will do something unexpected. Although they definitely do have the potential for disaster they can be a useful tool in a properly designed database.

I have occasionally implemented them without any problems but when using code that affects a cascade I always include a comment in the code to remind of this.