table relations and lookups

[bh75]

I have 3 tables. table1=schedule, table2=lookup, table3=job specs. I need information copied from table1 to table3 and remain on table3 even when record is from table1 is deleted which is why i have

a lookup table between the 1&3. My problem is when I enter a new record in table1 i cant seem to get that information to show up on table3. Are my relationships between the tables wrong? Please help, file attached.

-Rob Hunt

jobspecs_copy_1.fp7.zip

[innodat]

Hey Rob,

Your approach is right: because a job can be linked to more than one occurrence in the schedule table (and vice versa) you created a join-table you called "lookup". The basic set-up for a join-table is as follows:

Base Table 1 Join Table Base Table 2

Base-Table1: key-field 1 (linked to...)

Join-Table: key-field 1

Join-Table: key-field 2 (linked to...)

Base-Table 2: key-field 2

You seem to have doubled up the key-fields in your graph. If you follow the scheme above, it should work. Tipp: I would use record-ids as keys to link your tables; a field which is safe from being manipulated by the user.

Michael

Edited June 20, 2007 by Guest

[Søren Dyhr]

Yeah but to me was the template as clear as INK ...where does the abuse in the use of lookups in the field defs. fit into the whole picture, live relations must be more than sufficient!

Why aren't resources strained from the popups if occupied, each item for a job needs to go into the join table, and would guess that the approach isn't particular far from either:

http://www.nightwing.com.au/FileMaker/demos7/demo705.html

or

http://www.fmforums.com/forum/attachment.php?attid/10636/

--sd