> On 2014 Dec 1, at 07:28, Geoff Graham <[email protected]> wrote: > > If any part of your key value can’t be stored, then the whole key can’t be > stored (or indexed). > > You’re going to have to do the calc and store the result, which will then > index and link just fine.
Yeah, that’s what I was afraid of. My reluctance to do that was that having to copy the contents of the global field into each individual record that needs it is both (a) time-consuming and (b) the cause of auto-changing my “Updated” field with an irrelevant and misleading modification date. I was hopeful that my desired approach would work when I read the FMP documentation on how to establish relationships, where it specifically said that global fields can be used as match fields. I guess I’ll drop them a little note about the need to be a tad more specific in their writeups. Oh, well, on to Plan D. (Yes, I’ve already burned thru Plans A, B, and C on this one.) Thanks for the straight poop, Geoff.
