Thanks people, but the trigger doesnt really solve my problem. You see, there is actually a CHAIN of dependencies
whereB references A, C references B, D and E reference C and so on... So if i start writing triggers for all these,
there'llbe a huge process to follow. I'm not strictly against it, i might use it as a last resort, but i'm asking if a
simpleDML statement would solve my problem.<br /><br />Dear Shoaib, I did mention in a note that I don't want to
recreatethe 2 tables with the 'on delete cascade' clause. The tables are ALREADY created and populated. And they are
huge. So i cannot afford to drop and recreate them. I want an option in DML only. If that is possible that is.<br
/><br/><br />Thanks,<br />Shruthi<br />