Personally, I hate the term Many-to-Many. To me, it should be described as two 1-to-Many relationships with the parent and child swapping roles, depending on how you need it to function in a given situation.

For this reason, I recommend two forms. One that treats the Supplier as the parent with a child grid showing Products and one showing Products as the parent with a child grid showing all the suppliers for that product.

If you don't like that (and some people won't) then you can build a single form and add the "Parent" table twice to the Dataenvironment. The parent table would be related to the child table which would then also be related to the second instance of the parent under a new alias. When you moved the record pointer in the parent table, the child grid would refresh which would then refresh the "grandchild" grid.

HTH.

>Hi,
> I have two tables, supplier and product. That is many to many relation between thiese two tables becoz one supplier may sipply more than one product. And on the other hand, same product may be able to suppy by many supplier.
> How should I set the relation?
> I got cycle relation error!!
>
>Thank you