Olaf, thank you for all this help ! It works fine now :-))

My database was a small test database with no custom stored procedures. Still, I removed all existing stored procedures, but also all triggers, regenerated the referential integrity, and everything worked fine.

Then I understood what had been going on : before trying AMRI, I had tried the TaxRI builder, and that one set all triggers to _handleri(something), _handleri being a stored procedure from TaxRI. I probably wiped out the stored procedures, but left the triggers. When I ran AMRI, it just added its procedures to the triggers, making it "__ri_insert_child() and _handleri(something)".
So it was my mistake ; sorry, I really could have guessed all that by myself.

I'll test the builder a bit further, but everything seems fine, and it looks really nice, much better than the VFP builder. Thank you for the tip and for the help.

Regards,

David