This may sound oversimplistic, but I would have the application make sure that that no students are freshmen before deleting the freshman object.
That may mean looping over all of the freshman objects and promoting them to sophomores, deleting them, or (ack!) removing their class affiliation. There may be different strategies for handling different students. (Promote the A students and drop the rest.) Or it may mean disabling the delete button on the freshman form. Of course there plenty of other ways you could handle it. But that's a decision for your customer to make. I wouldn't have the gateway try to fix the problem itself. Patrick -- Patrick McElhaney 704.560.9117 http://pmcelhaney.blogspot.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
