Any reason not to drop the "bank account" bizobj on the form as a child of the "customer", and check New Child on New Parent on the "bank account" bizobj?

Then MM will handle all the adding stuff for you.

June
(another newbie, a little further down the learning path)

>Hi,
>
>I'm a new user of the MM framework and I wonder if somebody could give me a few pointers??
>
>My query is basically how best to organise my biz objects
>
>I have two related tables which have a one to one relationship, say for example 'customer' and 'bank account'
>
>For each of these table / entities I've created a seperate biz object and I've managed to do this without any problems.
>
>Some times I need to use the biz object indepdently of each other and this is fine, however I have a question about how best to have these two biz object 'talk to each' other.
>
>My specfic problem is this ;
>
>I have a form which is used to view / navigate / amend customer details. The bank account biz object doesn't really play a part in this form with the following exception.
>
>Whenever I create a new customer I have to create a new bank account record via the bank account biz object.
>
>I've tried using the event class but I unsure if this is correct way to do it.
>
>So on my form , I have placed my customer biz object and I have a event object which uses the 'defineparticipatingentities' method, which addd a reference to the customer and bank account biz objects.
>
>When the user clicks new on the toolbar my plan is to call the 'executeevent' method of this event class to add the required field values and link the two newly created records together.
>
>Is this the best way to do this kind of thing? or am I missing something fundemental here?
>
>Many thanks in advance, Bernard....