You can place a portal to Properties on your Contracts layout and vice versa. This works out fine for displaying data from that primary table, but editing data via the portal becomes problematic. Delete portal row in a portal to Properties deletes a properties record--possibly leaving a number of "orphan" join table records that can no longer link to that property unless you enable a cascading delete in the relationship. Delete portal row on a portal to the Join table leaves the related property record intact, but deletes the link to properties for that specifc contact record.
Interstingly enough, if you enable "allow creation..." for both the join table and Properties, you can add a new properties record in the portal and the linking join table will be automatically created. But trying to link an existing properties record to the current Contracts record cannot be done in a portal to Properties.
That makes perfect sense. I don't want to delete a property just because it has a new contact.
I have another question regarding join tables. How do I populate a join table for two existing tables each with hundreds of records and no common field?
Is it even possible?
If these were data written out on 3x5 cards--one stack for Properties and one stack for Contracts, how would you determine which contracts to link to which properties?
Yesterday was just too long!