We have two tables Assignments and Schedules.

An assignment can have 1 to many schedules.  A schedule can only have 1 assignment.

Due to how we have our reports set up, there is NO WAY we can have a foreign key back from Schedule back to Assignment. 

What we have is in the Schedule is a lookup field that points back to the Assignment table. When we delete the Assignment, that lookup field in the schedule table goes away.  

We have a trigger on the Assignment with a "BEFORE DELETE".  We fire off a class that attempts to delete all of the Schedule entries that are tied to it.  the code for that is below:

public class deleteScheduleRows 

{

@future

    public static void deleteRows(ID assignmentID)

    {

     Integer iCount;

     iCount = [SELECT count() FROM SFDC_Schedule__c WHERE Assignment__c =: assignmentID];

     while (iCount > 0)

     {

     List<SFDC_Schedule__c> newList = [SELECT id FROM SFDC_Schedule__c WHERE Assignment__c =: assignmentID LIMIT 900];

     delete newList;

     iCount = iCount - 900;

     }

    }

}

However, it seems that the Assignment is being deleted first, and its removing the lookup field value in the Schedule table so there is no way to remove the old rows.

I tried removing the "@future" from the class, but then when I attempt to create the list it throws an error about hitting the 1001 limit.

Any ideas?

Thanks

--Todd Kruse