I believe your problem might be here. I could tell more if I could see your relationship graph.
#If the company is a large company then set Active=No
If [ Get(FoundCount)>0 ]
Set Field [ EAInfoAll::Active; "No" ]
When your found count is > 1, the set field will only flag the first record to "No"
You would need a replace field contents here instead.
I understand that in this case you will mark that a company is "a large company" by relating them to them self in the "large company" database. Correctly understood?
Or will the record in the "Large company" table have records dividing in branches, size larger/smaller than X or?
If the first assumption is correct, that you only use this relationship to mark the company up against it selv to mark that it is a large company ... then a simple attribute field could be enough ... something like Large_small_ln where 1 is large and 0 is small. Or any other attribute that is helpfull to you.
But I might have got you wrong.
If it is because a large company might "own" many other companies you could consider just having one company table and a joint table to connect daughters to their mother company. Thereby only maintaining the same attributes (fields) in one table and only having one layout to care about?
thanks philip and carsten.
@philip: never knew that - one learns every day :-) thanks will try that out tomorrow (night here now)
@carsten - funny you mention this - I was just going to post a new question about exactly that.
see new question in board in 10 min. woud be great to hear your view there too.
Problem solved Philip, thanks again!