>>I have a basic design question about views.
>>
>>I've been placing multiple tables in one view where more than one of these tables is being updated by the view. I've been told that it's not a good idea to be updating more than one table in a view at a time. I had assumed that doing so whould acutally be better and more stable (as I only have to issue one tableudpate() command instead of 2 or 3) - but like I said now I'm hearing otherwise. Anyone have any thoughts on this?
>>Thanks!
>
>I think the views will get quite confusing when you try to update multiple tables.
>
>If you have a parent-child relationship, I think you should have one view for the parent (or use the table directly), and another view for the child. In any one of the views, you can show related fields from other tables, but better don't update them.
>
>Hilmar.

Well I've only been doing this for 1 to 1 relationships, wouldnt want parent/child tables in the same view,... but if I have one view that holds 3 tables with 1 to 1 relationships for example....that to me seems like it would be ok to update the 3 tables from within the one view..???? I mean I know it works but I'm hearing from someone else that it's a 'bad idea and not stable'...but to me it seems like a good idea and more stable...hahaha