Based on the code in the sproc you posted:
This is designed to do the same sort of thing as Access's cascade delete function.
Why don't you add a (referential) foreign key constraints with a cascade delete instead of trying to rewrite a functionality that's already there?
See BOL, section "FOREIGN KEY Constraints" for details.