FMPRO-L Archives

January 2011, Week 1

FMPRO-L@LISTSERV.DARTMOUTH.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: The Other Kind of Relationship
From:
Tim Mansour <[log in to unmask]>
Reply To:
FileMaker Pro Discussions <[log in to unmask]>
Date:
Mon, 3 Jan 2011 08:22:57 +1100
Content-Type:
text/plain
Parts/Attachments:
text/plain (27 lines) 
On 3 January 2011 06:39, Richard S. Russell <[log in to unmask]> wrote:
> Another possibility is to have the "Set" button create TWO records within PPLinx, 1 with Alan as Person A and Betty as Person B, and a 2nd with the order reversed. Again, this seems inelegant, especially given that there will come a time when these relationships change

It might seem "inelegant" but I suspect it might also be the most
straightforward solution. Your join table would then be simplified to:

PerSeqA
PerSeqB
Role

So long as you script the making/breaking of relationships to always
handle pairs of join records it shouldn't be too hard. You'll probably
only need two scripts with passed parameters to handle all situations:

Make Join ( fromID=123; toID=124; from="son"; to="mother" )
Break Join ( fromID=123; toID=124 )

The scripts just need to find any existing join pairs for the given
IDs and add/modify/delete them.

-- 
Tim Mansour <[log in to unmask]>
Neologica Print & Promotions ABN 63 904 335 408
Certified FileMaker 10 Developer
PO Box K1163 : Haymarket NSW 1240
Mobile 0405 500 846

ATOM RSS1 RSS2