Closing Application - Headstart bug?

Question

This mail was originally posted on the ODTUG maillist.
I am using Headstart Qms 5.0 and we are having problems with closing the
application window using the Windows Close button[x]. Detailed description
follows:
When window is closed by pressing the 'x' found at the right topmost part of
the screen, a message appears confirming whether to commit, not commit or
cancel changes. Once cancel button is pressed, it creates infinite loop or
sometimes shows the same message several times.
The temporary workaround was to comment out the before code added by QMS in
the key-exit trigger: qms$event_form('KEY-EXIT');
/* CGAP$TES_SEQUENCE_BEFORE */
/*begin
qms$event_form('KEY-EXIT');
end; */
/* CGNV$CLOSE_ALL_WINDOWS */
BEGIN
CGNV$.nav_enter_query := FALSE;
IF (:SYSTEM.MODE = 'ENTER-QUERY') THEN
exit_form;
ELSE
CGNV$.CLOSE_ALL_WINDOWS;
END IF;
END;
/* CGAP$TES_SEQUENCE_AFTER */
begin
qms$event_form('KEY-EXIT','AFTER');
end;
Although this solves the problem of infinite loop, this needs to be further
investigated because the code is actually handling the case where system
mode is 'ENTER-QUERY':
procedure close_current is
-- Purpose: Exit form, regardless of form mode
begin
-- Cancel query mode when running in query mode, and then
-- perform do_key('exit_form') as OFG generates code in KEY-EXIT trigger
to close
-- child forms when preference NAVCCF is set to Yes
do_key('cancel_query');
if name_in('system.mode') = 'ENTER-QUERY'
then
copy('10','system.message_level');
exit_form;
copy('0','system.message_level');
end if;
g_closing_current := true;
do_key('exit_form');
exception
when form_trigger_failure then raise;
when others then
qms$errors.unhandled_exception('qms$form.close_current');
end close_current;
Looks like a Qms bug to me. Is anyone familiar with this? All help highly
appreciated.
Rgds,
Siggi

Answer 1

This reply was originally posted on the ODTUG maillist.
I ran into this problem. It was a Forms 5.x bug. It was definitely fixed
in 6.0. I can't remember the patch set in 5.0 that fixed it. It was not a
Headstart problem, but rather a Forms bug.
Mari Cobb
Oracle Certified Professional
Independent Consultant
Sacramento, California www.ms-mari.com
null