Doug,

I have, essentially, 2 sets of tables: court case tables (some of which are mentioned in previous posts) and incoming case tables. The only commonality between them are some definition tables, and maybe this is the cause of the problem (and please tell me if this would be considered a "circular relation".)

Here's a bit more info:

CourtCases (primary key is COURTCASESID) related to:
Defendants (primary key is DEFENDANTSID) related to:
People (Name - primary key is PERSONID)
Charges releated to:
OffenseDefs

IncomingCases related to
InDefendants related to:
People
InCharges releated to:
OffenseDefs

There are other defintion tables used by both sets of tables, including one that has relationships between CourtCases and IncomingCases.

Oh, OK, I think you DO considder these releations a "circular relation"? Guess I was thinking (?) that the relation, somehow only goes from Primary Key table to the other. Do you see any way around this at the moment?

Thanks for your time. J

>Hi Jill.

>This can happen when you have circular relations ie. A -> B -> C -> A or A -> B -> C and A -> C, which appears to be the case here. As a result, SFQuery finds several ways to get from A to C and may not choose what you and I would see as the best path. Fortunately, I've rewritten the join engine to handle cases like this better, and once I've tested it more thoroughly, it'll be available in an update.
>
>Doug