>>>>I have a table with one-to-many relationship to itself. The delete
>>>>option in the referential integrity is cascade.
>>>>
>>>>When I try to delete the parent record I receive message trigger failled. Why if I use delete cascade?
>>>
>>>Did I miss something? What is a table with a one-to-many relationship to itself???
>>
>>It's a way of storing hierarquical information. The table has a field that could point to another record at the same table (it stores the primary key of other record).
>>It could be used for example in the UT database. I don't know if it's like that here, maybe Michel could tell us later :)
>>It would be something like this message you're reading would store the primary key of your previous message. With a cascade deletion, deleting Antonio's original message should also cause the deletion of your response and mine.
>>
>>Did you get it?
>>
>>Renato
>
>Today is my lucky day, I guess as I am learning lot of new things...
>
>I didn't know that this kind of relation can be created...
>
>Thanks for Info !!

Nor did I (obviously :-) )...but now to answer the post....

Will VFP create a solid trigger for that kind of cascade? Seems to me that if you don't write the stored procedure yourself, VFP could end up creating a recursive nightmare.

Where is the trigger failing? Try tracing the trigger and watching where it first returns a false.

HTH