I Am working to set up database and it looks like a classic many-to-many relationship.  but don't know how to set this up in Sesame higherarch structure.  Expect to have a Top Form for Cusotmers database with sub form showing line items for services/products purchased.  But also want to have a Top Form for Parts with a subform showing all Customer purchases of that service.  It sounds like three databases but is really only two databases.  How do I set this up using the naturale order that Sesame works with?

to do something like this you'll need to use a junction table

you'll have to excuse me as this is in SQL I haven't used sesame in a while:

http://en.wikipedia.org/wiki/Junction_table

Using junction tables shouldn't be a SQL specific task. Again I haven't touched sesame in a long time,
but you would need three tables: Employee,  Safety Class, and  the junction table.



+---------+                +----------------+               +-------------------+
|Employee|                | JunctionTable  |                |                        |
|             |                 | emp | safety  |                | Safety Class      |
+---------+                +----------------+               +-------------------+
|1           |                 |   1       |  A     |                | A | ISO9001      |
+---------+                +----------------+               +-------------------+
|2           |                 |    2      |    A  |                | B | Chem spills   |
+---------+                +----------------+               +-------------------+
|3           |                 |     2     |    C  |                | C |pointy objects |
+---------+                +----------------+               +-------------------+
|4           |                 |    3     |     D  |                | D | germs         |
+---------+                +----------------+               +-------------------+
|5           |                 |     2     |    B  |
+---------+                +----------------+

_________________________________________________________________

Note that on both Employee and Safety Class both have unique IDs (Primary Keys) 1,2,3,4,5 and A,B,C,D respectively.
Now on the JunctionTable you see that that neither employee or safety class entries are unique, they are what is called foreign keys,
that is  the "emp" field in the junction table is a foreign key for  the employee table and  safety field from the junction table is a foreign key for the
safety class table.

in essence you'll use a third table to "join" the two tables together.

Hopefully this explains it a little better, as you don't need SQL  to do this, It was just the example it used, Sesame should do it just fine.

obfusc88 wrote on Jul 9^th, 2007 at 5:39pm:


Keep in mind that a subdatabase can have only one natural parent. Depending on what you do, one or both of your links may want to be relational.