Therefore you should define KEY-XXXX triggers for those keys that you would like to users to use, then include KEY-OTHERS to disable the rest. TAB key is KEY-NEXT-ITEM trigger; so define a KEY-NEXT-ITEM with the built-in function NEXT_ITEM According to Reviews: 8. Feb 08, · Key-Others at the block level will only override a form-level Key-Others. It will not override any other form-level triggers. You must either override all the form-level triggers at the block level, or add code to the beginning of each form-level trigger such as. In short I would like to store the ascii value of combination in a variable and accordingly make the form fire the key-others trigger event. Report message to a moderator Re: How do I capture what key has been pressed by user [ message # is a reply to message # ].
Key others oracle forms
do_key('commit_form'); would fire the KEY-COMMIT trigger, if there is one. If there isn't one, it will just do the default action of that trigger, which is a commit. Any key triggers would be in the form itself, most likely at the form level, and you would view the triggers using Oracle's Forms Builder. May 29, · Programming Function Keys Posted on May 29, by cmadmin Questions derived from the 1Z – Oracle Forms: Build Internet Applications Oracle Self-Test Software Practice Test. In short I would like to store the ascii value of combination in a variable and accordingly make the form fire the key-others trigger event. Report message to a moderator Re: How do I capture what key has been pressed by user [ message # is a reply to message # ]. Jul 23, · So I cannot use Oracle terminal to change the values of the key-strokes since other forms in the same bin should not be altered. I was thinking that maybe I could trap the key-stroke with the Key-Others trigger, but it looks like it only traps key stokes that are not previously defined. Oct 13, · Add every other 'Key-' trigger with a matching message statement. You will need a single accessable item in a block on a canvas but you don't use it. Compile and run the form, and when you press your various function keys it will tell you the Oracle Forms facility that matches it.I have seen hierarchies as follows: Item. Iconic. Button. Normal. Button. Button. OK. Button. Cancel. Button. Other. Button. Small OK. Button. Text. Item. And so on . I have a form with several fields that contain a LOV's. Other function keys (like F11/Ctrl F11 for enter/execute query) are working fine. Oracle Forms includes navigational, validation, and database .. A Key-Others trigger fires when an operator presses the associated key. As we mentioned in early posts, KEY-OTHERS will trap all keys which are not defined in the form. Therefore you should define KEY-XXXX triggers for those keys. I have a requirement to reverse the Page-up, Page-down vs the Ctl-Page-up, Ctl- Page-down on a single form, but it remain normal for all other.