>>
>>Brett,
>>Would you try this :
>>
>>SELECT P.Username, P.Phone, C.KidFirstName, C.KidLastName,
>>S.Status, Pr.Priority
>>FROM force Parent P ;
>>left join StatusLookup S on P.StatusKey = S.StatusKey ;
>>left join Child C on P.ItemKey = C.ItemKey ;
>>left join PriorityLookup Pr on C.PriorityKey = Pr.PriorityKey ;
>>WHERE P.Username = "SMITHBOB"
>>
>>Cetin
>
>What does the FORCE do? And why did you convert Parent to P, Child to C etc?

'Force' forces order of joins in the way they're written. I wrote aliased versions (P,C) which is commonly used in order to shorten SQL string + ease of writing. ie: if I had too many fields listed with StatusTable. each field would add 10 bytes to SQL string.
Cetin