<i><font color="#663300"><i><font color="#663300">Is there a way to have a view that uses multiple tables for display purposes, yet allows the user to update the main table in the view? Or is it a basic suggestion to keep the views to be updated based on a single table which will be updated.</font></i>
The general consensus in this forum is to update only one table per view. But nothing prevents you to show readonly information from other related tables in the same view.
This raises an interesting point. Consider the scenario:
A client table has a number of fields which contain references (cid's) to a number of tables which are displayed in comboboxes - Title, PostCode (zip code to most of you!), Suburb, State are good examples. When the view is created in the database you are only allowed one table join and even then the view insists on both tables being updateable.
Is the solution to hard code the view? and if so where does it go?
©2001 graeme thomson |
