A good idea, I'm not sure if it will work for me but I'll give it a look.

The potential problem is that the view parameters we use to requery the views are tied to properties of the parent objects in some cases, which are not refreshed when the delete is fired off. But I can probably clean all that up and use method calls that access the table values which should return empty or null values. And I can replace my cascading delete calls with cascading refresh calls.

Thanks!