Hi Kamal --

Yeah, I know about avoiding the View Designer. I usually write PRGs or SPs to create views and DBSETPROPs but I wanted to be >slick< and try the View Designer, but it screwed up the keyword order that when I looked at the SQL my brain vapor locked :-)

Thanks again.


>Rule of Thumb : If you have 3 or more tables and more than 1 outer join, view designer is not the place.
>
>It saves a lot of time maintaining the view for such a case from a seperate program instead.
>
>>Thanks. I was trying to use View Designer and it was misplacing certain keywords in the SELECT statement and I couldn't remember them....this was embarrassing, almost like forgetting your kid's name or something :)
>>