Exiting form after being in query mode

Question

Hi guys,
Having an issue with some forms after migrating from forms version 6i to 10g. Learning as I go along.
Forms which startup in query-mode seem to have an issue when closing - all have two blocks - one block is utilised through user query and the other (like a child) displays the query results and can be updated from here. If the user does not enter a query they can cancel it using exit_form which works fine.
After a query has been completed the system mode returns to 'normal' mode (which I can see through debugging by entering messages/pauses throughout the code). However when exiting the application breaks with error FRM-92100. I have had this problem before with regards to exiting forms but I got round this by having an open window (acting as a parent or root window) in the background which is not closable. Been tweaking the form all afternoon including using exit_form(no_validate) and other changes. By commenting out enter_query and execute_query commands the form closes as normal without issue which means it is related to query mode or something along these lines.
If anyone has any ideas or pointers on how to move forward with this it would be much appreciated.
Cheers,
Robin

Answer 1

Guys,
Thanks for the replies.
The form currently uses exit_form twice in order to close the query mode and I receive a message "query cancelled" to confirm this.
I have also tried - and retried for the benefit of confirming this - the code you have mentioned u3 - using it in the when-window-closed trigger. I chose <option> to be no_validate.
The main app is opened from a webpage. Forms are opened from a menu which is attached to all forms. The code that opens the forms is open_form (i.e. not call_form or new_form) for modal reasons.
The application is disconnected straight after exit_form is used - its as if coming out of query-mode to normal causes this as I said before closes gracefully when I remove the enter_query command.
As for the error message itself here is a fuller picture:
FRM-92100: Your connection to the server was interrupted. This may be the result of a network error, or a failure on the Server. You will need to reestablish your session.
Details...
java.lang.NullPointerException
at oracle.forms.handler.TextComponentItem.selectionChanged(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextComponent._fireSelectionChanged(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextComponent.select(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextField._selectAll(Unknown Source)
at oracle.ewt.lwAWT.lwText.LWTextField.processFocusEvent(Unknown Source)
...AND SO ON!
Hope this gives a better picture of what's going on :)
Robin
update - There is a 'dirty' workaround to this problem - if i minimize the window (change its state in any way) after the mode is back from query-mode to normal THEN close the window it closes gracefully.
Edited by: Robin84 on Sep 10, 2008 10:03 AM