Cascade updates

[Tarnish]

Hi all,

I've got some old apps with cascade updates set in many of the relationships. Nearly all of them (maybe all of them) are autonumber primary keys that aren't seen by users, and certainly aren't exposed to users for editing.

That would seem to mean that the cascade updates is never going to do anything. Is it worth editing those relationships? Will/Does cascade updates hurt performance?

Thanks.
T

 

[MajP]

I have never heard of a problem (especially in your case where it is never used). If it is a possible issue it is not significant. Did not make the top 100s

http://www.fmsinc.com/tpapers/faster/

However if you designed a db where you are updating the primary key often with a lot of related tables I would think you could corrupt your data. I would never design a db that way. Most people try to find a key that never or rarely will change.

 

[Tarnish]

Thanks for the reply, MajP.

I've been through that list before, but forgot all about it!

T

 

[MajP]

Here is another good resource, did not make this one either.

http://www.granite.ab.ca/Access/performancefaq.htm