>
>Can you explain the behaviour you want? writing your own referential
>triggers is a piece of cake.
>
>Actually, for stable lookup tables, my argument is that, if you design them
>properly, you will never delete or update a key and so there is no
>referential integrity to protect, no need for any foreign keys at all for
>lookups.

OK - what I have done (to allow the user to update values in lookup tables)
is to write the original value into the primary table when the value is
inserted into the primary table.

In other words, the primary table now has a "taxrate" field. This field
holds the tax rate at the time that the record was inserted. In this case,
it will allow the user to update the tax rate field without changing the
value in records in the primary table.

Is this the kind of thing you mean, Helen?

Thanks

Tim


[Non-text portions of this message have been removed]