You could use the OPEN_FORM built-in procedure instead.
Something like this:
Using the ‘SESSION’ parameter you tell the forms runtime engine to open a different database session for the called form, which you can commit or rollback without affecting the calling form.
I’m not a forms guy so I asked my forms people and they replied with this:
The originating form had changes on it before going to the second line… This is not allowed… If they commit those changes before going to the second form the problem would go away.. Changing from this
To something like this
If :system.form_status <> ‘QUERY’ then