Lets see if I can simplify that:

DataBase A DataBase B

rec_ID == link (relationship)

In order to establish all the records in DataBaseA that are NOT related to B, my idea was to kind of "invert" their relationship. But how?

I need to get all the records where link::link is empty... right?

I tried it get these records, introducing the field:

checkout_link = link::link

and the self relationship in DatabaseA:

checkout_link =/= rec_ID as the relationship

but it doesn't work. Why? Checkout_link is supposed to be empty...

I can get these records in find-Mode (seeking for the empty link::link), but I want it to be done with a seperate relationship, and even -Go to related records, Find omitted is no solution

Any Hints

Then you need a new relationship, using the "not equal" predicate.

Thanks, but that's exactly what I did... and it doesn't work!

Most likely because the not-equal relationship links a field that is based on a related content from the first relationship... there must be a way!!

I don't think you make a relationship to an empty field.

hmmm... it seems as if I can't make the point clear.

It's not that I want to build a relationship to an empty field.

Again: I need to get all records that are NOT related by relationship A

If there wheren't any further constrains, Go to related records/Show Ommited would be what I want to be done...

If you have relationship from table A to table B were field A1 = field B1. Then I think what you want is a new relationship between these 2 tables were field A1 <> field B2. <> is the not equal sign.

Create a calculation field in Table A of IsEmpty(Table B::serial) and perform a find for 1 in this field.

why isn't it then possible to relate that field IsEmpty(Table B::serial) to a global=1 to get them in a portal without the perform find routine?

I did it, but it won't lead to the correct rsult.

and to Ralph, relationship 1 is between B and A, while relationship 2 must be self related A A, because its there I retrieve the records from. Inverting with not equal leads to chaos

... I think I stick to the workaround with the find procedure

Neither the IsEmpty field nor the global can be indexed. Therefore a relationship cannot be created between them in either direction.