Per Jerry Whittle:
Now if you use artifical primary keys, such as an autonumber with no
"meaning", there really isn't a reason to use cascade update as you should
never have to change the primary key data in the parent table. BTW: I
almost
always user autonumbers for the PK.
That's where I'm coming from except for some lookup tables where
I want an ID value of zero to represent "[NA]".
As in:
tlkpReferenceRateType
-----------------------------------
0 = Unknown
1 = Libor 3-month
2 = Libor 6=month
3 = Fed Fund Target.... and so-forth
-----------------------------------
Where I got caught was copying table values from another app and
deleting unused values - leaving gaps in the sequence.
The gaps got me when I was flipping the data on it's side with a
column for ID#1, a column for ID#2... and so forth. My code was
such that the missing values resulted in empty columns.
No big deal to change: I just enabled cascading updates in all
directions from the lookup table and changed the IDs as
desired...
But the process got me thinking about it and wondering if
cascading updates might be a good SOP when setting up tables in
general.