>James,
>
>The way MM works is you save the Parent information, then save all the Child information for that Parent. What I am looking for is a way to save information in the Lookup and have it available immediately, not after the Parent.Save(). For this to happen, I would need to save the Lookup information, and requery the lookup view. This would leave that information if the Lookup base table regardless of the outcome of the Parent.Save()
>
>I was looking to see if this is possible, and how to accomplish this.
>
>Thanks
>
>Rex
>
>>>Kevin. et al
>>>
>>>How can I add new information to my comboboxl.RowSource view 'on the fly'?
>>>
>>>Example:
>>>
>>>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.
>>>
>>>Have you had to solve this problem? How?
>>>
>>>TIA
>>>
>>>Rex
>>
>>Check out the cancel child on cancel parent option and the requery child on delete parent option in the bizobj (page 3). This should take care of the problem.

Now I understand. Would you consider writing a custom save method in your bizobj that called the save method of your child bizobj? For instance:

Commandbutton.click()
Thisform.oBizobj.CustomSave()


Primarybizobj.CustomSave()


IF vartype(childbizobj) = 'O'