>Hi Paatric,
>
>Usually, persistent relations established within the database container do not have compound indexes. As a matter of fact, I don't know how you would do it with the drag and drop desktop of the DBC. For persistent relations used to enforce referential integrity, why not relate the foreign key in the child table into the primary key of the parent. This should allow for the proper behavior of rules when inserting, updating and deleting record.
>
>You can use compound indexes in your procedural code and forms. This will not disturbe your presistent relations and RI code that live in the database container, even when you have a compound index set in a form, for example.
>
>LelandJ

Thanks for the reply, Leland. Since it was an issue I recently inherited (yes, I'm trying to distance myself from the whole thing!) I just coded an update routine for the child tables.... The user is phasing out this software as we speak, so I hope to not see it again!

Thanks again,