Frank,

Have you considered sending the proposed to be saved child dataset to the parent BO as a parameter for a rules check? Not exactly sure how to do this, but it seems the logical way to handle this.

Alternatively, you could allow the save to take place regardless of parent total not equal to sum of children, but set a status field on the Receipt (add a new column for status if not already there) that shows that the Receipt is not in balance or in error. Then, when dealing with Receipt headers down the road you would know to ignore Receipts in error status.

HTH

>Linda,
>
>but at the point in time when the Receipt BO is being saved, the Receipt Detail would not yet have been saved, so I need to sum what is currently in memory, not what is stored in the database. Or am I thinking too hard about this?