>Hi
>
>I have just finished setting all my joins and running my referential integrity builder to generate the code for my joins. However, after I did that, it caused a problem with my GetKey stored procedure for auto-generating primary keys.
>
>On some of my talbes (child tables), when I went to append a new record, I received an error message> FAILED TRIGGER.
>
>So, I went back to my RI builder and changed all my "restricts", to ignore and everything works fine.
>
>My question is this> Is that just a patch? Because I believe I want to "restrict". I took a FoxPro class a month ago (Because I am very new to this!), and the instructor said to always restrict on the insert column in the RI Builder.
>

If you tell VFP to restrict inserts, then it will restrict them by Giving a "trigger failed" message and rolling back your changes. This is what restrict inserts does.

Can you describe the table scenario that you have that you believe you need this type of RI with? Possibly we can figure out where the design wet wrong...