Larry,

Ran into that issue immediately. The easy way out was to remove any FK reference that interfered with the cascade delete. I am having some instance I think) that the cascade delete didn't work even though the tableupdate() returned .t., but I need to do a little more study.

Kevin


....One other quick note. Foreign key constraints are checked prior to any trigger firng in SQL Server. This could present a problem if you want to handle RI using triggers. The constraint will prevent the deletion in the parent table from occurring (if records exist in the child) and therefore neither the initial deletion nor the cascade deletion will take place.

FWIW, I heard at NOLA that SQL Server 2000 will have cascade deletes and updates.....