Re: [SQL*FORMS] A multi-table block?

Steve,

You may as well just create a view defining the UNION and leave it there all the time. The only overhead involved is to read the View definition before executing the query. I the form is used often the view and its underlying statement will probably be cached continuously anyway.

There is a way of replacing the default block query, but Forms3 developing is now receding into the mists of memory. I'm pretty sure that the processing required is less efficient than defining a view.

Cheers,

PT

3srf_at_qlink.queensu.ca (Frampton Steve R) wrote:

> I am creating an SQL*Forms 3.0 application, which consists
> of 3 blocks. In my first block (MASTER), I am displaying
> the employee information. The second block would display
> the absence records that belong to the current employee.
> The third block is inconsequential at this time. :-)
>
> The union would do the trick:
>
> select bla bla bla
> from current_table
> where conditions
> union all
> select bla bla bla
> from history_table
> where conditions
>
> If a view is the only way this can be accomplished, does it
> sound reasonable to create/replace the view upon KEY-STARTUP
> and drop it upon KEY-EXIT?
>
> Thanks in advance.
Received on Wed Oct 30 1996 - 00:00:00 CET