>>>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?
>>
>>I don't know if it is the best solution, but I use parameterized views for the child and grandchild. I don't set a relation. The parameter for the child is the parentkey, and the parameter for the grandchild is its parentkey. I also have code for my grid that makes the selected record highlighted, even when the grid does not have focus.
>
>Sorry, are you saying grandchild's parameter is the child's primary key? That will mean you need to commit your changes each time you change your child record, right?

I should mention that my grandchild table isn't exactly a grandchild. It's more like a younger brother. I have a table of "things", related many-to-many with a table of "documents". In my "document" form, there is a grid for the view "thingdocs", which lists the things for a single document. Its parameter is document.dockey. The "things" table has another child called "authorizations". My "document" form has another grid for the view "thingdocauth" which has the authorizations for the currently selected thing in the thing grid of the document form. Its parameter is thingdocs.dockey. In this form, "authorizations" is acting like a grandchild. But I don't edit authorizations in this form. For that, I go to a simple parent-child form which has thing fields on the form and authorizations in the grid.

My Save button does TABLEUPDATE on each open cursor.