Hi Cetin,

Thanks...overnight I got thinking that it would work just as well to have one view for each child table and then another for the parent....a bit more work but simpler anyhow. Also, when I looked at the result set created by the multi-table view (i.e. a browse), I am sure the next guy in here would say "what the hey..." when they saw it!

Thanks for responding (thanks to Victor as well).

Albert

>>Hi Everyone,
>>
>>I have routinely used a two table view to delete a parent record and it's child records. Have used the view designer to do this and it works fine. But have just run into a case where I have a parent table and this table has 4 child tables related to it.
>>
>>When I tried to work up the view in the view designer, it seems to create it okay (somewhat) - and I used LEFT OUTER JOINS as not all the child tables will always have child records.
>>
>>Anyhow, could not save the view to try it out. Should I be able to do this in the view designer or do I have to do a hand-coded view? or maybe I have to do 4 different views, one for each child table?
>>
>>Thanks,
>>Albert Gostick
>
>Albert,
>My personal suggestion: Never use a view to update/delete/insert more than one base table.
>
>Next simple or complex I suggest to create views in code (and generally include FORCE clause so designer can never open it and screw).
>Cetin