Re: Forms 4 base tables

A couple of things to consider:
1. from my experience large views (many columns) are slower than a parent-child relationship.
2. Depending on what you do, you may have trouble updating data from a view.
3. You can have a child relationship with only one record. Create a separate base table block on the same canvas with a link to the parent block, it'll look the same to a user. Let oracle do the work. 4. You can also create a separate block on the same canvas and manually control the data by programatically configuring the default where clause defined in the block.
5. I always suggest using base table items instead of created text items because you can program the data edits directly in the database instead of needing reams of code.

Hope that helps,
Lewis

Derek Scherger <dscherger_at_sierrasys.com> wrote:

>Hi folks, in the Oracle Forms 4.0 Motif designer there is an
>option to set the base table for a block to select data from.
>What is the best approach to use if I have several tables that
>I need data from in the same block? Currently we are thinking
>views should be fine, but are there any alternatives, and what
>are their pros and cons?
 

>Thanks!
 

>Derek
Received on Wed Aug 23 1995 - 00:00:00 CEST