Re: Developer Forms 5.0 FRM-41009 "Function key not allowed." ADDITIONAL INFORMATION

From: Mike Rainville <Michel_at_cc.mcgill.ca>
Date: Sat, 13 Mar 1999 00:36:30 GMT
Message-ID: <36E9B2E5.EE5F5417_at_cc.mcgill.ca>


Greetings,

 New information for

Oracle Developer 2.0 Forms 5.0 FRM-41009 "Function key not allowed."


Symptom: FRM-41009 Function key not allowed.

(1) Important: the problem occurs for the empty form (Enter-Query?) BUT NOT after the
master and detail blocks are populated. Minimize the populated form - no problem; minimize with an empty form - it happens.

(2) The problem is definitely related to my logging procedure
 (INSERT, COMMIT)
(3) The problem is eliminated if the call to the log function is disabled
(in the listed situations)

(4) Even if the logging is disabled by an IF-THEN-ELSE within the procedure,
 the problem remains

(5) Oracle does not identify for the specific "function key" which is in conflict

(6) Based on the list of situations(below), I suspect the COMMIT (via either COMMIT
WORK or Commit_Form at an unusual time is the source of the difficulty, or perhaps multiple commits closely spaced.

  • MY_INITIALIZE procedure called on initializing or re-initializing form
  • WHEN-WINDOW-ACTIVATED form-level trigger runs on open, restore, subform open etc...
  • MY_REQUERY_BY_NAME procedure called from button
    (to pre-load or reload the record group with a list of names and IDs
  • MY_KEY_SEARCH_LOV procedure called from Menu, Display_List or button beside a key (to prepare and show List of Values)
  • MY_EXIT procedure called from KEY-EXIT Trigger (Form level)

Related Oracle problem reports: SQL*Forms References: 573798 (03 Sep 1998)

                                                                      and especially
565149 (09 Jul 1998)

Present situation: About 50% of the log entries had to be disabled for beta testing. The application will not be put into production without a functional log. The key problem is to IDENTIFY the "function key(s)" causing the failure.

Except for annoying and sometimes misleading error dialogue box, all functions are working correctly and producing the expected output.

Thanks for any help,

Mike Rainville
Montreal, QC, Canada Received on Sat Mar 13 1999 - 01:36:30 CET

Original text of this message