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
