I have a perfectly working lookup for field2 that comes from related table based on values for field1.

Now it turns out field1 that defines the realtionship for this lookup needs to be field1:: table2. This breaks the lookup.

So, I have created calcfield1 (results in text that gets the value from the field1::table2) and that calc works just fine.

But when I try to build the lookup on a relationship with calcfield1, but the lookup won't work.

I noticed that a relationship based on a calcfield1 won't allow indexing; so, I tried to use textfield1 with a calculated result (which can be indexed) based on the calcfield1 value but no values show up in textfield1 upon which to build a relationship and so I still don't have the lookup.

I am sure there is a work around but I am kind of at the end of my resources:)

Thanks as always.

If you are using an auto-enter calculation, you will need to manually populate the field for existing records.

Thanks queue -- is there no way to establish a relationship where one side is a calc that will allow lookups?

If it is an unstored calculation and cannot be indexed because it references related, global, or other unstored calculation fields, then it cannot be used on the child (to) side of a relationship, only the parent (from) side.