I'm not quite sure if I've understood your scenario but you might like to try this.
In the view designer add all your tables and when asked which type of join arbitrarily select.
On the upper pane select each of the links (black lines) in turn and delete each one.
Now go to the Filter page (NOT the join page) and add the links between tables and table fields, prefixing each on the example side with a "?" question mark that you need to be linked. I'm not sure but I perceive that the query works more efficiently if the variable parameter e.g vp_custid is the last filter entered, but this may just be an illusion.
Do the rest of the View designer as normal.
<i><font color="#663300"><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?
</font></i>
©2001 Geof whitham |
