Hi,
I am stuck with the following, maybe simple, problem:

(simplified example)

- one table (T1) with two fields: items (F1,text) and unique/duplicate
(F2,calculation field, unstored, based on a self-joining relationship
in order to mark unique/duplicate)

Problem: I would like to display only the unique items from T1 in a
portal in a second table (T2, relationship:
unique(F2,T1)=unique(f1,T2). I can't do this because I can't establish
a relationship based upon an unstored calculation field.

Current solution: I implemented a second auto enter text field (F3) in
T1( auto enter value from calculation field F2) and based the
relationship on this new text field which I can store and index
(relationship: unique (F3, T1)=unique (f1,T2).

O.k. - great, this works, but this is not good enough.

Now, when I delete an item from T1, the relationship does not get
updated automatically. In other words, let's say I delete an item
which is three times in the database (T1). One is marked unique, the
other two are marked as duplicates. If I delete the one item which is
marked unique, the calculation field (T1,F2) gets updated for the two
other items left correctly (one will be marked unique, the other one
as duplicate), but not the auto-enter field (T1,F3). It looks like the
auto-enter field does not get updated upon changes in an unstored
calculation field. Therefore, the relational database table (T2) is
not going to display the unique items correctly - the formerly
duplicate item which is now unique is not displayed.

How could I solve this dynamic problem? Any help would be really
appreciated.

Bernd

On Apr 3, 7:28 am, wollsch... (AT) gmail (DOT) com wrote:
What version?

G

Filemaker 8.5


On Apr 3, 4:05 pm, "Grip" <g... (AT) cybermesa (DOT) com> wrote:

You can use an unstored calculation in a relationship, but it will
only work one way, only if the calc is on the 'parent' side. By
parent in 7.0+, I don't mean anything intrinsic to the relationship
itself, but rather how it's being used. If your relationship is
T1::UnstoredCalcField = T2::TextField, then the layout should be based
on T1, showing the portal based on table T2. In essence, Filemaker
can 'filter' stored values through the one instance of the unstored
calc (the live record), but it can't 'pull' all the unstored calc
values.


Grip

On Apr 3, 8:41 am, wollsch... (AT) gmail (DOT) com wrote:

Thanks for the information Grip, but this will not work in my specific
case.

Do I have any other options?

Bernd

On Apr 3, 10:49 am, wollsch... (AT) gmail (DOT) com wrote:
This newsgroup (like most and with good reason) does not permit the
posting of files. I recommend going to:

http://www.fmforums.com/forum/

and posting your question with a sample of your file there.

G