Hi hilmar,

>I have solved this particular problem for myself. However, I still want to take a good look at your TaxRiBuilder eventually. Too busy right now, but what I heard, it sounds interesting.

>My solution simply involves copying parent first, then child. But that would pressumably still be slower than turning RI off completely, right? Since every record still has to be checked.

Yes, indeed. The bad performance of the VFP RI builder lies in the mechanism that opens and closes tables for each record. Normally this isn't a problem for one or two records, but when processing a lot of records, the VFP RI mechanism is getting the bottleneck of performance.

The TaxRiBuilder offers you a mechanism to let the tables open and close them manually after you're done. This has a huge impact on performance. In internal tests some REPLACE and APPEND commands have been proven to be 900% faster than with the normal VFP RI. Actual performance depends on a number of things (like network performance and number of related tables etc.)

Further the TaxRiBuilder delivers far more readable and more compact RI code. TaxRiBuilder is upwards compatible with the VFP RI builder, (you only have to install it, and in the DB designer choose for the TaxRiBuilder instead to the VFP RI Builder)

Walter,