Home » Developer & Programmer » Forms » Oracle Form : navigational problem in data block (Oracle developper forms9)
icon10.gif  Oracle Form : navigational problem in data block [message #389234] Fri, 27 February 2009 13:44 Go to next message
Messages: 1
Registered: February 2009
Junior Member
Overview of the problem

We are in environment where we have codes and tables from an existing third party company.
We are allowed to modify coding(opensource);
However, we are very reluctant to change baseline tables.
Consequently, we have chosen to create reference tables if we need additional fields.
Essentially, these reference table have the same keys than the baseline tables.

Problem definition:
The form related to employee info, had 3 components:
Header block(capturing employee no)
Data block 1 (table 1 with emp_no as Primary key with other fields)
Data block 2 (table 2 with emp_no as Primary key with other fields)

I created a new block called
Data block 3(table 3 with emp_no as Primary key)
This table (NOT baseline) contains my new field.
If it was possible, I would have added this new field to data block 1(table 1).
My new field is displayed in the same group of data than data block 1.

I created a relation(master-detail) between baseline table 1 and my new table 3; because I want to take advantage of the cascading delete. It a one to one relation between table 1 and table 3.
If I delete one employee in table 1 , it will be done for table 3.
If I insert one employee in table 1 , it will be done for table 3.

With this design I am not able to give to the user the feeling that the field in data block 3 is an extra field of data block 1.

When the user use NEXT BLOCK function, the navigation is very confusing for the user.

Is there a better way to proceed???

Thank you in advance!
Re: Oracle Form : navigational problem in data block [message #389243 is a reply to message #389234] Fri, 27 February 2009 14:46 Go to previous message
Messages: 20849
Registered: June 2005
Location: Croatia, Europe
Senior Member
Account Moderator
Perhaps you could create a non-database item in Block 1. Block 3's item may remain hidden - set its "Copy Value from Item" and/or "Synchronize with Item" properties to Block 1's non-database item. Doing so, you'd be able to perform inserts.

As of queries, populate this non-database item in the Post-query trigger; once it is there, you may update it if necessary.
Previous Topic: if Hiredate > 01-jan-09 then go_block('emp')
Next Topic: % progress bar
Goto Forum:

Current Time: Fri Oct 21 17:46:17 CDT 2016

Total time taken to generate the page: 0.35335 seconds