>Rex,
>
>>I have an inventory transaction form. In the form I have a Parent of v_Inventory with a Child of v_InventoryDetail. The Child has a Lookup (DropDown Combo) of v_InventoryLot which is related to Child by an iInventoryLotId field. If I add a new element in Lookup and execute a Lookup.Save(), then cancel the Parent transaction, I still have the Lookup entry.>
>
>The cleanest implementation is to not save the Lookup until the Parent is saved. You can make the Lookup cursor table buffered so you can add new records without having them saved to the source table until you're ready.
>
>Regards,

Leave it to Kevin to come up with a simple, yet elegant solution!