Re: Forms 5.0 Master/Detail blocks

Paul's approach does have the advantage of easier reuse, on the other hand the FROM Clause Query means that everything is encapsulated in the form itself, and you don't have to get the DBA to add the view to the schema. The choice may depend on whether this particular join is unique to this form, or one you plan to reuse.

In practice I often find that I 'prototype' the view as a FROM clause query, then create it as a view before deployment.

Paul Dorsey wrote:
>
> Another nice technique is to build an updatable view
> and base your block on that. Actually, I like that better.
> You encapsulate your code (easily reused) and minimise
> both coding and network traffic.
> --
> Paul Dorsey
> Dulcian, Inc.
> www.dulcian.com
> 212 595 7223
>
> igal_at_healthstreet.com wrote in article <6ippp6$obs$1_at_nnrp1.dejanews.com>...
> > In article <354DBA4F.FD4189C8_at_vpha.ufl.edu>#1/1,
> > Frank W Phillips JR <FWP_at_vpha.ufl.edu> wrote:
> > >
> > > In the detail block of a master/detail I need to replace code value
> > > fields which the text descriptions of the code. I know I can create
> > > display items and populate them via a trigger, but I would rather do
> > > this in a standard SQL join fashion (a query that does a table join to
> > > get the data). Thanks in advance for any help…
> > >
> > >
> >
> > Why ?
> > And if you insist - try ... Powerbuilder.
> > Igal
> >
> > -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> > http://www.dejanews.com/ Now offering spam-free web-based newsreading
> >
Received on Thu May 07 1998 - 00:00:00 CEST