in the form method :(form event = on Load) or if you have a tab control, in the code for managing the change of the tab page
you would put some code like this : relate many([Parent_table]parent_Key) or Query([Child_table];[Child_table]Parent_key=[Parent_table]parent_Key) see Relate Many command description in the language manual, or the online documentation, or the (html) help files (I use these, so I do not have a link to the online page). It gives a good description. Relate Many is good if there is only *1* relation from the parent, however it triggers all relations and so can have side effects. As a side note - I suggest that all your relations be set as MANUAL not as AUTOMATIC. Automatic relations will do the relate many command for you - BUT - can have nasty side effects if you have circular relations as it will cascade through the relations. ex: [Table A] -> [Table B] -> [Table C] -> [Table A] with automatic relations, starting at [Table A], related record from [Table B] will be located, and then related records from [Table C] will be located, after which (and this is where your problem comes in, [Table A] records will be loaded that are related to [TAble C]. THIS can change the current record(s) in [Table A]. On Tue, 11 Oct 2016 13:50:37 -0300, pk paul wrote: > > @Keith > Hello Keith, thank you for the reply. Yes, I did, however, I do not see how > they implemented the join or related record selection for use in the > scenario I am mentioning, which is where I am having my difficulty. I am > sure it is a common scenario, I am just missing something :) ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
