>>>You can open Parent Table Properties (in Table Designer) and put your custom stored procedure name into Insert Trigger Box. Then you open Stored Procedure editor and write your custom code (under this procedure name) to insert values into appropriate tables (I guess it should be some UPDATE_SQL commands). It's a good idea to have some customized error messages when you return .F. from trigger.
>>
>>Thanks Edward.
>>
>>Now in my referential integrity builder should I ignore or restrict my insert? As far as my experience goes it's slim, so bare with me.
>
>You should 'Ignore' in RI builder.
>
>Using the UPDATE_SQL command how should I go about appending blanks to the tables? I don't have much experience using SQL.
>
>Use INSERT-SQL for appending records with pre-defined values (it's much better than using blank records).

INSERT INTO works great, but I found that if I attempt to recall the record after deletion the uniquess of my index fails. You know a work around for this? My plans are to add the deleted record to my history table and just recycle the deleted record. Now if I have say, ten deleted records in in my parent and child tables and add a new record, I search the parent for a deleted record, scatter blank to a variable then gather it and assume adding the person. I believe I will have to add this same recycling code in my RI. Do you have any better ideas and a way to recall my records if necessary?

Thanks again Edward

Jon