Hi Jon,

Very strange. You're using the same database for your tests in VFP 7.0 and 8.0. If not and index could be corrupt or something.

At this time I did not have any reports of the TaxRi code failing, so I could very little for you at this time. The best you can do is to place a set step on at the beginning of the _RIHandle procedure and find out where things go wrong. If you can find out, please give me a mail and I can see what I can do for you.

Walter,


>>I don't know the exact answer to your question, but why don't you try my TaxRiBuilder available from the files section. It will run perfectly within VFP 8 and should also take care of additional function after the RI function in the INSERT,DELETE and UPDATE triggers.
>>
>>The TaxRiBuilder has many advantages over the normal Ribuilder. For example: it's more flexible, faster, creates compacter and more readable RI code, but is fully compatible with the standard RI builder.
>
>Walter,
>
>Thanks for the suggestion. I do like how your builder consolidates everything into one procedure.
>
>However your RI builder does not work successfully with our data. Perhaps it's because of the number of tables and/or relations. I was able to generate the RI with TaxRIBuilder and not get the error that VFP8's builder produces. After the generation, I found that I was able to insert a record without a problem into a table with garbage data when a trigger violation should have been fired (i.e. the foreign key was intentionally invalid). This trigger fires perfectly with VFP7's builder having generated the RI.
>
>Ready for other ideas??
>
>Laterness,
>Jon