>... snip
>
>Customer-orders-lineitems is a popular demonstration model. But why change the parent once you have the child? Seems like a bad design or bad analogy.
>

Probably a bad analogy. It's not an order but something that can belong to different customers at different times, thus the need to change the owner when it is sold.

>... snip
>
>>I guess from an OOP point of view, the customer lookup form should be stand-alone and not be dependent on the order form providing it with the lookup view.
>
>If you want to make the form independent and use it elsewhere, you should probably consider a private datasession for it, to ensure it doesn't change anything on the other form. On the other hand, if this is its only use, sharing the datasession and manipulating the same bizobj, you shouldn't have to pass the value back, just set it how you want it from the modal form.
>

Is manipulating a second view in the bizobj (if that's what you call changing the record pointer) considered to be manipulating the bizobj?

Thinking again on the conept of bizobjs and forms, the cListObjEditForm kind of works similarly to what I want to do in that the callingform and calling list bizobj are passed in, not coded on the form. Just when I thought I had it figured out...

June