>>>>>>I am curious. How do most of you do 1-many-many form? Use parameterized view on the child table and grandchild table and set filter to the grandchild while the child is moving? Or Use parameterized view on the child table and grandchild table and set relation between the two? Or use normal view on both and relate the 3 generations together?
>>>>>>
>>>>>>Is there a best solution?
>>>>>
>>>>>My preferred solution is with parameterized views. Use requery() whenever you need it.
>>>>>
>>>>>José
>>>>
>>>>Does your grandchild refer to your grandparent instead of parent key?
>>>>
>>>>If you requery whenver you navigate your child record, you can't keep them in the buffer.
>>>
>>>I am not sure I understand you quite well.
>>>
>>>Let's say cid is the primary key in the parent, cParentId the foreign key in the child and cChildId is the foreign key in the grandchild table. If you requery on cChildId in the grandchild view, all should be fine.
>>>
>>>José
>>
>>If you use parameterized view for both child and grandchild, you will have a problem. For example, you requery on grandchild when you are at child record 1. You modify grandchild data. Then you move to child record 2 and want to modify grandchild data for record 2, you have a problem. You need to commit your changes. Otherwise, you will get uncommited data.
>
>Shihchau,
>Of course you have to commit the changes. I work with bizness object and have one per level, ie one for parent, one for child and another for grandchild. My framework senses when I move from one bizobj to the other and reacts accordingly. ie it will propose me to save my changes in grandchild if I move from one child to another.
>
>José

Thanks. That is what I want to confirm.