On Apr 23, 2008, at 3:35 PM, Karsten Weinert wrote:
> This is a real clever technique, thank you. Can you advise me where to
> call new on the child bizobj? As I tried to explain above, the
> onValueChanged handler seems not to be appropriate. Setting
> NewChildOnNew / NewRecordOnNewParent to True would not help in all
> cases, as it may occur that a given parent row has no child.
I'm not sure that I understand. Do you mean that if you are editing
an existing parent that has no child, the user could add information
that would require a child record to store it? In that case, I would
add code to the requery() and afterPointerMove() method of the parent
bizobj to call a method in the child; this child method should add a
new record to itself if its RowCount is zero. The beforeSave() is
already there to cancel empty children, so this should not cause empty
records to be saved.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
