I thought I knew how this worked!

I have a relationship between two tables that is based on a compound join involving two fields.

Like this...

table a::g_date = table b::date

table a::id = table b::id

The date field in table a is a global field. I also have a field in table a that sums related records in table b. Like this...

table a::net = sum ( table b::net )

If I ask it to find records in table a where table a::net is null (=) it works just fine. If I then perform the same find but this time check the omit box it returns records where table a::net are both null or have values. I would haved expected only non null values or where there were related records in table b.

What am I missing here. This is running on a server by the way.

Edited March 31, 200817 yr by Guest

I may be wrong here (so, comment, pls review!), but I don't think that the multi-predicate relationship that includes a global is valid when in Find mode. Therefore, you need to Perform your Find in Table B and then gtrr match found set Table A.

I don't think I would put it quite that way. In any case, it shouldn't matter whether a relationship is valid in Find mode or not, because (paradoxically) a search is NOT performed in Find mode - otherwise nothing would be ever found when searching non-global fields.

I don't know what the problem is here. Based on the description alone, I believe it should work the way fmsavey expects it to work.

I don't think the issue has to do with the global. I often have trouble performing omits on related fields with null values. Instead of using the = with an omit, instead use just the * with no omit.