>That is what I understood from this sentence in your article :
>>This program offers some interesting additional options. One option that I find very interesting is "Allow blanks", for the "Insert" case. The idea is that you can leave a field blank, but if you write a value, the referential integrity functions do the verification in the other table, to see whether it is a valid value.
>
>The possibility to have referential integrity on nullable fields is important to me, so this alone would already be a reason to research for TaxRI...
Ah, I had quite forgotten about that.
While I didn't actually use it, the idea is to have RI that either (a) forces you to have a valid FK, that is, one that is contained in another table, or (b) leave it blank.
The options which I found most useful was to disable RI temporarily. This is sometimes useful when you need to update data.
Also, I like the nice and compact code - about 1/10 of the size of the code created with the standard RI-builder.
> (I have not found it yet).
Download #
9923Unfortunately, it is tricky to find this one.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
