>>Ivan,
>>
>>You don't have to set relations between tables. The idea is that every business object has a main VFP cursor and you update only one cursor per bizobj. Once you set the relations between the bizobjs, the framework takes care of filling the foreign key in the child object etc.
>>
>>I have a white paper on my website (in Spanish) describing the DE methods.
>>
>>José
>
>
>Hi José.
>
>It's amazing the feeling of starting all over again. I'm a bit lost here. Ok, I set the relations between the bizobjs. In the child, use the bizobj builder and in the "Parent/Child Settings" filled the "Parent object" field. Now the child knows its parent. But how does it know the field in the parent DE used as reference ? It's tragic to have this kind of question, isn't it ? But it's fun, I'm laughing at myself a lot lately !
>
>BTW, I'll have a look at your homepage now.
>
>Thanks.

Ivan,

I don't know exactly how the MM framework solves this issue right now. In my version of Codebook, I have a cParentKeyField to do what you search for.
The MM documentation is excellent. I'm pretty sure it's explained there.

José