Erik -- thank you for your reply to my trigger failure problem. I took your adivce and placed a (0) in the ntitle_id field in my parent tables, and that did the trick. After I did that, I was able to append records to my child tables without getting the trigge error.

Is this a bad design practice.... to simply add the (0) to the first field. You offered other solutions that I didn't attempt to do. This seemed to be the path of least resistance!

For this particular application, I feel this may be fine. It is going to be a web-base application. The user will not be able to touch any of the tables or append records. They will simply be on line clicking various buttons and extracting information through the queries we are building.

I just needed to be able to data entry information in myself for this project. I will be the only one touching the tables, beside maybe a person doing data entry work. Do you feel this will be ok, or should I take your advice and use "code", to allow me to append records without getting the trigger failure (assuming I am restricting on the insert tab of the referential integrity builder)?

That would be an undertaking in itself. It took me 3 weeks to learn how to auto-generate primary keys with a stored proceedure and a keylist table!! I have to admit though, I feel I could teach a class on that proceedure.

Thank you very much for your response. I don't know what I would do without the help of people like yourself on this site!

jcd