Colin,
Not sure if I fully understand what you're trying to do here, but here's what I'm
hearing:
You have a portal in Clubs of all the Members belonging to each club. You want this
portal to display the Member's name, which is an ebase field held in File C (probably
Names_.102). Do I have this right?
If so, create a calc field in File B. For example,
DispName (calc, text) = Name::Person 1
Since this field uses a related file, it must be unstored. But no worries. Once it's
present in File B, even unstored, you can then stick it into your portal in File C.
FMP does make you go through the intermediate step of the calc field in the "join"
file, which is what your File B is (since it joins instances of people and clubs).
Really, the difficulty is with portals, since they are set to one relationship only.
You can't go two relationships deep through a single portal.
Does this help?
Matt
At 06:44 PM 11/2/00 -0500, you wrote:
>Not a direct question regarding ebase, but kind of related (ahem):
>
>I have three files linked via relationships in the following manner:
>
> File A (Clubs)--> File B (Members) --> File C (ebase)
>
>"File B" displays basic ID information (i.e., name) from "File C" and also
>adds additional demographic info to this (student ID, age, race, sex, school
>attendance/history, etc) as well as associating each record with a
>particular club.
>
>File A "marries" the information in File B with infomation on Volunteers (in
>another file) and displays all club participants (members and volunteers) in
>two portals (side-by-side).
>
>I thought that I would be able to display the "name" shown in File B within
>File A, but I cannot. In other words, I can only display related
>information ONE FILE AWAY! I knew that this was a limitation in FMP with
>CALCULATIONS that depend on a relationship, but these are simply text files.
>Of course, I could make the "name" field in File B a LOOKUP, but this sort
>of diminishes the value (i.e., decreased file size) of using related files,
>doesn't it?
>
>Ultimately, I will merge all info in "File B" directly into ebase (File C),
>so this will become a moot point (I am keeping them temporarily separate
>because I may be obtaining this student information from the local school
>system's database, and wanted a "temp" file to dump this info into before
>importing into ebase). It is disconcerting to realize, however, that I can
>only utilize the relational concept ONE FILE AWAY in FMP!
>
>Am I missing something, or is this, in fact, a limitation of FileMaker Pro??
>
>Tanks Expurts,
>Colin
>
>
>
Matthew Scholtz
Evaluator and IS Coordinator
Health Initiatives For Youth (HIFY)
www.hify.com
