I get it. The main benefit is you don't have to program the restrictions when you can set them up in the view. Otherwise it seems to me to be the same thing as editing the table itself.
On Wed, Oct 5, 2011 at 11:57 AM, A.G. IJntema <[email protected]> wrote: > The difference between a single table based view and a multiple table based > view is that you are able to update a single based table view.**** > > The difference is the added where clause to the table which creates the > view. **** > > ** ** > > There are circumstances thinkable when this could be very useful.**** > > For instance if you only like to show rows in a table (view) which are > allowed to be updated. You don’t need any ‘where-clause’ programming anymore > using this view in various forms.**** > > ** ** > > Another example is restricting access to a table for employees.**** > > They only have access to rows which are relevant to them and the where > clause in the view creates this restriction automatically.**** > > ** ** > > Another advantage is you are able to change the selected rows in a form > without leaving the form, the only thing you need to do is changing the > parameters of the where clause (and a refreshment statement like recalc > tables).**** > > ** ** > > And so on**** > > ** ** > > Tony**** > > ** ** > > ** ** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *William > Stacy > *Sent:* woensdag 5 oktober 2011 20:23 > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - RE: limit results on a child table in a > master/detail form**** > > ** ** > > What is the difference between a view that "is based upon a single table" > and editing the table itself? I've always thought of views as being > multiple table creatures. **** > > On Wed, Oct 5, 2011 at 11:08 AM, A.G. IJntema <[email protected]> wrote: > **** > > Dan,**** > > **** > > In my opinion using a temporary view in which you can define a dynamic > where clause is a beautiful solution**** > > Advantages: The view is unique per user and you are able to change the > where clause dynamically, even on the fly.**** > > If the view is based upon a single table you are also able to add, update > and delete rows from the original table.**** > > **** > > Tony**** > > **** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Dan > Goldberg > *Sent:* woensdag 5 oktober 2011 19:21 > *To:* RBASE-L Mailing List > *Subject:* [RBASE-L] - limit results on a child table in a master/detail > form**** > > **** > > I have a master/detail form that I need to put a where clause on the detail > portion of the form.**** > > **** > > I have tried:**** > > **** > > EDIT USING purordernew arrange shoploc by part ORDER BY vendor# where > shoploc.invweek = 'p'**** > > **** > > It does not work. If I remove the where clause the form opens but not with > filtered data.**** > > **** > > I am thinking I will have to do a view for the detail table(shoploc) but > was hoping there was a better way.**** > > **** > > Does anyone know a better way to do a where clause on a detail table of a > form?**** > > **** > > TIA**** > > **** > > Dan Goldberg**** > > **** > > **** > > **** > > **** > > **** > > **** > > > > > -- > William Stacy, O.D. > > Please visit my website by clicking on : > > http://www.folsomeye.net > > > **** > -- William Stacy, O.D. Please visit my website by clicking on : http://www.folsomeye.net
