We are developing a custom application to be incorporated into the
Oracle Applications Framework. We are running Oracle Financial
Applications release 11.0.3 and Oracle Forms version 4.5 on SUN Solaris
2.6. Since the Application Object Library Developer's Guide is very
high-level and lacking in detail, we are looking for some better
documentation/resources to assist with the development.
We have run into some inconsistencies and are trying to determine what
is causing them, Forms or Apps:
- When navigating between fields using the mouse, especially fields in
different blocks or alternate regions, the cursor/record pointer is
often not moved or moved but then jumps back to the location where it
came from.
- When deleting parent records that still have child records on the
form, recieve message that 'parent cannot be deleted when children
exist' even though the block is set to allow cascading deletes.
- In some cases, records are not deleted from the database but instead
have a flag set to indicate the record is no longer active. This is
handled in the ON-DELETE trigger for the block. The block's where
clause only allows selection of active records. When deleting parent
records in which child records have been deleted (i.e. record not
displayed to the user; inactive in DB), receive message that 'parent
cannot be deleted when children exist'. This occurs as soon as the
user attempts to delete, prior to save process being started. Our
understanding of how Forms handles database activity is that DML
statements (i.e. inserts/updates/deletes) are not executed until the
user initiates the save process. Therefore, the block should only be
concerned with what is displayed/cached in the form.
Any assistance on these issues is greatly appreciated.
--
Robert Kopf
Map Mobile Communications, Inc.
Sent via Deja.com http://www.deja.com/
Before you buy.
Received on Wed Mar 08 2000 - 13:16:04 CST
