Page tree
Skip to end of metadata
Go to start of metadata

In Oracle Forms, developers specify the number of records that should be shown in the UI and it renders that specific number of records, even if the number of actual records is smaller. So if it's specified that the block should show 5 records, 5 records will be rendered, even if there are only 2 records of data. This is uncommon in modern applications and the Frames framework follows a different approach.

Whether you're using gridview or repeater controls to represent multiple record blocks, the current implementation of these controls only renders records if there are actual records of data to be shown to the user.

This causes an expected difference in terms of user experience, mostly when the user is entering new data. In Oracle Forms applications, users tend to enter new records (in multiple record blocks) by one of the following approaches:

  1. Press the create record button in the toolbar
  2. Press the create record keyboard shortcut
  3. Press the next record button in the toolbar (only applicable if the current record is the last record)
  4. Press the next record keyboard shortcut only applicable if the current record is the last record)
  5. Perform a mouse click on one of the empty records (shown below actual records of data)

In the migrated application, the user can use any of the approaches above except the last one (approach number 5), because there are no empty records rendered, for the user to click on.


Approaches 1 through 4 may produce a different behaviour if the behaviour of the create record or the next record actions is redefined through an action trigger. For instance, some applications have a patterns to redefine the next record action, so that, instead of moving the a new record, it shows a message informing the user that they are in the last record.