I have a child db with fields sport, participation status, and department related to main db with fields: sport, participation status, and department. The child db has C for participation status. The portal is in the child db and sees only records for the sport, dept and "C" only. The relationship window is: child db on left and main db on right.
Charlene M. Flora Administrative Assistant Division of Athletic Training/Sports Medicine Intercollegiate Athletics for Men and Women The University of Texas at Austin P. O. Box 7399 Austin, TX 78713-7399 512/589-0480 This message is for the designated recipient(s) only. It may contain privileged, proprietary, or otherwise confidential information. If you have received this message in error, please notify the sender immediately and delete the original. If this message contains Protected Health Information as defined by the HIPAA Privacy Rule, any dissemination, distribution or reproduction by a designated recipient to an entity not authorized by HIPAA Privacy Rule to have access to the information is strictly prohibited. -----Original Message----- From: FileMaker Pro Discussions on behalf of Peter Kilcoyne Sent: Thu 10/8/2009 1:03 PM To: [email protected] Subject: Re: Relationship Issue Geoff, Steve, and John: In my original database relationship Table_Jobspecs (MarComProjects) is related to Parts via ProjNum=ProjNum_job AND Constant=Constant_Job. I duplicated the same relationship and swapped Constant and Constant_job with Mail and Mail_job naively thinking this would work and changed the name (since you can't have two named the same) to Mail. This maybe where I went wrong. Comments? Also if I un-index the fields Mail and Mail_job nothing shows up. Peter On Oct 8, 2009, at 8:37 AM, Geoff Graham wrote: > On Oct 7, 2009, at 4:51 PM, Steve Cassidy wrote: >> ... > >> But then I've now had a further glass of wine. I could be wrong. > ... > > One more glass Steve and you may attain true clarity. > > Peter, > > The line from the starting table occurrence (the layout) to the > destination table occurrence (portal content) is not what your > portal wants it to be. Now if you're sure the portal is set right, > that leaves your relationship graph. It's one of the two right? You > ruled out calculations evaluating from the wrong context. > > I'd start troubleshooting by placing another (temporary) table > occurrence in the graph that is what I think it should be, then > bring a related field into an unused area of the parent's layout. > I'd expect to see the first related child record's data. Then a > simple 6 line portal over that. A serial field or some other > identifiable data from the related records would be my choice. Kind > of a take it from the top approach. > > I've certainly fought this one before. > > Geoff
