>Download #9923

>Unfortunately, it is tricky to find this one.

Thank you, I got it and will install it.

>>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 Foreign Key, that is, one that is contained in another table, or (b) leave it blank.

In fact I confused "blank" and "null". With the standard RI builder I tested that it is in fact possible to enter null values, but not blank values. As the default value of an INSERT SQL command seems to be blank rather than null, it is still useful that blank values can also be allowed.

>The options which I found most useful was to disable RI temporarily. This is sometimes useful when you need to update data.

Yes, this is a clear plus.

>Also, I like the nice and compact code - about 1/10 of the size of the code created with the standard RI-builder.

This is not so important in my case. We need to make VFP work as much as possible like a real relational database because we know that some time we will upgrade. So I would modify automatically generated code only in last resort.