>Hi hilmar,
>
>>The tricky part is to copy parent table before child table (avoid "trigger failed"). Also, if you have a lot of data, it helps to compare table structures and skip tables that haven't changed (use COPY FILE instead).
>
>Therefore you might want to take a look at my TaxRiBuilder in the files section. I use it to turn RI off in such particular cases. It also is a lot faster (when using the fast) than the original builder when appending record. In a lot of my products I use the same strategy (Of copying a new empty database and appending new records) and works fine. Only when the database grows too large it might be a slow option.
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.
Hilmar.
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)
