>PMFJI Mark, but I was curious if the un-nesting is just to improve readibility or if there is a performance improvement. Thanks
>
>>To follow-up, the problem is the designer nests the joins. You can use the designer to create the view initially, but before you exit the designer, view the SQL generated, and copy the code to a PRG. Un-nest the joins then run the PRG. e.g.,

>>FROM Travel!TravAuth ;
>>  LEFT OUTER JOIN Travel!Roster ;
>>    ON TravAuth.EmpId = Roster.EmpId ;
>>  LEFT OUTER JOIN Travel!Accounts ;
>>    ON TravAuth.ActId = Accounts.ActKey

Technically, there is a performance improvement because the nested joins cause an error when you try to use the view. :) On the other hand, I have had a query with nested joins work as long as the join types were different, but I do not remember which combination actually worked.