KEY-CERREC TRIGGER IN ENTER-QUERY MODE

hi all,
i want fire key-crerec trigger in enter-query mode, how it can be done.
i am using oracle 10g r2.

first: Why did you need such a trigger? In Enter-Query-Mode it is impossible to create new records.
second: Forms has a problem with some triggers in some modes. That means, that some trigger didn't fire in enter-query, but in older versions of forms they do. So, maybe you run into one of this problems

Similar Messages

Form trigger - fire in enter query mode

Hello,
Could someone help me with the following problem, please?
I want to create an key-exeqry and I want it to execute in enter-query mode. Unfortunatly Designer set's the property 'fire in enter query mode' for the trigger to 'No'. I can't find any setting to set it to 'Yes'. Does someone knows a setting or a work-around?
I'm working with designer6/headstart6.
Thanks in advance,
Martine.

Sandra,
I tried to put the key-exeqry in the template. There's only one problem the key-exeqry is a 'in place of' trigger. When I put the code 'Null;' in the trigger, a generated form without a key-exeqry doesn't work because the 'key execute query' does nothing. A generated form with a key-execute query works fine.
At the other hand, when I put the code 'Execute_query' in the trigger, a generated form without a key-exeqry works fine, but the other one doesn't.
Which code should I include in the template-trigger?
Thanks,
Martine.

Hotkey "Create Record" while the form is in enter-query-mode

pressing the hotkey F6 for create-record while the block is in enter-query-mode results in the error - message:
Function key not allowed. Press Ctrl+F1 for list of valid keys.
The error-occurs although I created a trigger KEY-CREREC. The trigger isn't executed
In older Forms versions the behaviour was different. Is there a way to let the form work like in the old versions?

thnx for reply.Problem not solved.
i m trying to assign the value of text item to a variable in pre-query trigger. i m able to get the value into variable when the string in the text item does not startwith <,>,=. but when the string starts with any one of the operator (<,>,=) it gives error.
lenth of variable is 1000 charaters, and text item's max leanth is just 4 charactres.

FRM-40200 and FRM-40501 in Enter-Query-Mode

Some strange behaviour in Enter-Query-Mode:
Although the help states
About Designing Forms for Querying+
+.. To make a "query-only" block, set Query Allowed to Yes and Delete Allowed, Insert Allowed, and Update Allowed to No. ..+
I get FRM-40200: Field is protected against update.
System.Mode says, we are currently in ENTER-QUERY.
Setting insert- and update-allowed to TRUE, I get
FRM-40501: ORACLE error: unable to reserve record for update or delete.
The entered character flashes and is erased immediately.
Any ideas?
Forms 10gR2
Items are base table, all transactional properties aund query_allowed are true, query_length is ok.
2 Things that happen before the initiation of the enter-query-mode:
. data-source is changed to another view; column names are ok.
. all block-items are disabled and not navigable at start-up of form and re-enabled and made navigable before entering the block.
The values of block and item-properties mentioned above are take at WHEN-NEW-ITEM-INSTANCE and no further trigger fire.

I think you are not meaning just the KEY-ENTQRY-Trigger, that to easy
IF INSTR(:SYSTEM.TRIGGER_BLOCK, '_DETAIL') = 0
+ AND :SYSTEM.TRIGGER_BLOCK NOT IN ('VZG_KOPF','KONTROLL','BUTTONS','TEMP')+
THEN
+ ENTER_QUERY;+
END IF;
.. but the rest is a lil bit, let's call it bulky; including pll and db-packageges.
I hoped to get a clue, if somebody has a similar expeience, in what direction to search. It's strange.
And, as I noticed today, it's not a problem of all forms of the app. Not even of all the forms called from the same "environment" (same globals, same menu-form from which they are opened). To me it looks like Enter-Query does not work in the forms where I switch the block-data-source from a view to a globally temporary table. That (this switching) is not a new feature and Enter-Query worked in the past. Althoug we had some changes in the temp tables in the last weeks there are no problems in querying the data in the forms. Recompilation of pll and fmb, no improvement. And either Enter-Query woks in a form or it does not.

Disabling LOVs when not in enter query mode

hello. I currently have a form in which a master block populates a detail block. when the master is populated the cursor automatically goes to the detail block and sets it to enter query mode (due to the face that there are multiple details but the user may only view one at a time). To select the appropriate detail the user may select the detail from a LOV which is activated by clicking a button. once the detail has been selected and the query executed there is no real need for the LOV as the user can now edit/delete the detail. Also when adding a new detail there would be no need for the LOV as the presence of it would only confuse users. So basically the only time the LOV is usefull is during query mode to query the detail the user wants to edit/delete.
In your experiance how would you acheive this result?
Any help would be greatly appreciated.
Thanks

well you can write a trigger Key-listval on your LOV item to check the mode of the block
if :system.mode = 'ENTER-QUERY' then
list_values;
end if;LOV will only display in enter query mode only

Change Value of Veriables in Enter-Query mode

hi all
I have made a search utility on a table, there is reqirement that in the enter-query mode the user can enter any combination of character, in simple words there is requirement of %% at begining and at end of desired search field.
as :system.last_query gives the value like
SELECT ROWID,SEQ_NUM,TAG
FROM sequel1.sequelsql WHERE ( UPPER(TAG) LIKE :1 and (TAG LIKE :2 or TAG LIKE :3)) order by TAG
how to pad % sign in the veriables :1,:2 and :3 as need to search
tag like ('%ASSESSMENT%')
thanks in advance

SELECT ROWID,SEQ_NUM,TAG
FROM sequel1.sequelsql WHERE ( UPPER(TAG) LIKE :1 and (TAG LIKE :2 or TAG LIKE :3)) order by TAG
1.
have you tried to handle the items contents in a PRE-QUERY trigger ?
If blk.item IS NOT NULL Then
:blk.item := '%' || :blk.item || '%' ;
End if ;2.
You could change the WHERE clause (or the ONETIME_WHERE)
in your KEY-EXEQRY trigger:
Declare
req Varchar2(512) ;
Begin
req := '( UPPER(TAG) LIKE %' || :blk.item1 ||
'% and (TAG LIKE %' || :blk.item1 || '% or TAG LIKE %' || :blk.item3 ||'%)) order by TAG ;
Set_Block_Property( 'blk', DEFAULT_WHERE, req ) ;
Execute_Query ;
End ;Francois

[ Forms10g2 ] Default item value in Enter-Query mode

Hello!
How could I specify default value for an item in Enter-Query mode? E.g. I press KEY-ENTQRY, and :L_YEAR item gots current year as a default search condition (though it may change). I've tried to implement it this way:
<pre>
Enter-Query;
:l_year := extract(year from sysdate);
</pre>
This work in a rather awkward way. If I run this once (e.g. as a result of a hotkey press), it just enters Enter-Query mode, but if I run this twice (by pressing hotkey second time) it fills :year variable and does search with it as a search condition! Then, I've tried to go straight and wrote:
<pre>
Enter-Query;
:l_year := extract(year from sysdate);
Enter-Query;
:l_year := extract(year from sysdate);
</pre>
Well, this didn't work. And SYNCRONIZE call before the second Enter-Query didn't help either. So, my questions are: 1) how can I achieve needed behaviour? 2) What's going on in my experiments? Why :L_YEAR gets assigned on second keypress (as in first experiment) but not on second subsequent call (as in second experiment)?
Thanks in advance!

I don't know why that won't work but I have something which might:
when-new-record-instance trigger:
if :system.mode = 'ENTER-QUERY' then
:l_year := extract(year from sysdate);
end if;It's always best to use both the block and item names...:block.l_year

Do_Key in Enter-Query mode

Hello,
I have a WHEN-BUTTON-PRESSED trigger that has do_key('list_values') that brings a calendar. I use calendar.pll library. It works, when the system is in normal mode. But when the system is in enter-query mode it does not work. It says "Function key not allowed". What is the alternate solution, other than calling the calendar functionality from a new form?
Thanks in advance.
Arun.

try this out,
go_item('item_name');
execute_trigger('key-listval');
specify the item name for go_item

EXIT_FORM in enter query mode

Hi Guys,
I have a button on my form to exit the form code is:
EXIT_FORM(No_Validate);
when my form is in enter query mode the button does not work. i have to cancel the query first and then the button works.
How can i change my mode to exit form even if it is in enter query mode.
Please help its urgent.
thanks , Imran Baig

HI Imran,
That is quite normal. If you press CTRL/Q, it executes an implicite Key-EXIT trigger. If you are in Enter Query mode, this will close the query and does nothing else. When you execute it again, you leave the from without validation.
My suggestion were: Place the exit_form(no_validate) twice in your trigger--the second would be absolute harmless, since the form will no longer be active, provided you came from Normal Mode. Otherwies, it will force leaving the form by first closing the query and then leaving.
Regards, Miklos Herboly.

FRM:41361 Cannot navigate out of form in 'Enter Query Mode'

Hi,
I am using a master - detail block in my form.When I query the master block I am getting this error message
FRM:41361 Cannot navigate out of form in 'Enter Query Mode'
I have given DO_KEY('ENTER-QUERY') in WHEN-NEW-BLOCK-INSTANCE trigger of master block.
and in property palette of Master block I have given the next navigation block as Detail block.
According to the value which is queried in Master Block the Detail block should be populated.
My form should open in 'Enter Query Mode'.This problem always happens from second time onwards
I open the form.When I open the form first time this problem is not occuring.
Can anyone suggest a solution for this
Thanks,
Nasiya

Have you written a Key-EntQuery trigger at the Master block or the form level,
If yes, then can you put that code here.
The NEXT-NAVIGATION-BLOCK is only used for navigation when you use a next-block built-in on a key-trigger.
Have you written a ENTER-QUERY command on any trigger that fires prior to the said WHEN-NEW-BLOCK-INSTANCE trigger?
If yes, then thats the reason that the first time you run the form, your form is in ENTER-QUERY mode.
Also, maybe execute on enter-query fails and hence the blocks are not getting populated.
Also, ENTER-QUERY is always on a single block. And while the block is in enter-query mode, navigation out of that block is prohibited.
you have to either have a successful EXECUTE-QUERY or use:
EXIT_FORM(NO_VALIDATE) to come out of ENTER-QUERY mode.

Suppress the enter-query mode when no-data-found after execute a query.

HI,
Greetings of the day, Can any one suggest me that how to Suppress the enter-query mode when no-data-found after execute a query on the form by a button.
whenever i execute query on form and result is no data found then form :system.mode is still in enter-query mode.
i want that if result is no data found then form comes back it initial state.
i will thank full of him who will help me..
Thanks in Advance..

Put this in your Key-ExeQry trigger:Execute_Query;
If Get_block_property(:System.current_block,query_hits)=0 then
Exit_form; --this cancels the Enter-Query mode; Does not exit the form.
End if;You may want to trap and prevent the "FRM-40353: Query cancelled" message, and change the "FRM-40301: Query caused no records to be retrieved. Re-Enter" message. To do that, you need an On-Message form-level trigger:Declare
Msg_Code Number        := MESSAGE_CODE;
MSG      Varchar2(150) := SUBSTR('   '||MESSAGE_TYPE||'-'
                         ||TO_CHAR(Msg_Code)||': '||MESSAGE_TEXT,1,150);
BEGIN
If Msg_Code=40301 then
     -- 40301: Query caused no records to be retrieved. Re-Enter
    Message(' NO RECORDS FOUND',No_acknowledge);
Elsif Msg_Code=40353 then -- Query cancelled.
    null;
Else
    MESSAGE(MSG,NO_ACKNOWLEDGE);
End if;
End;

FRM-41361 Cannot navigate out of current form in Enter-Query Mode

Hi All,
I am getting the FRM-41361 error in the bottom message area when opening a form from the function navigator. The issue does not exist when opening the form from the application homepage. The form is loaded in enter-query mode, and the enter_query command is in the WHEN-NEW-FORM-INSTANCE trigger. I have checked all triggers that fire after this point for any type of navigation but do not see any. The interesting thing is, if I put a fnd_message.set_string and fnd_message.show just before the enter_query call to debug, the issue goes away entirely.
Is it possible there are security triggers firing after the form is loaded into enter-query mode that could be causing this and that the fnd_message calls are indeed buying time for those triggers to complete before the enter_query call?
Any help/advice is appreciated. Thanks!
Dan

Yes, when I looked through the triggers I made sure to look for go_block and go_item calls as well as any calls to leave the form.

How to display LOV on web in ENTER-QUERY mode with form or block query only.

Hello all
How can I display lov automatic on the web in from enter-query
mode in form or block query only mode.
thankx

If I understand correctly your explanation, your called form
fails to activate the LOV in enter-query mode when it is deployed
and test on the browser.
So lets proceeed like this, to make it work in all environments,
let us programetically activate the LOV.
HOW?
In the called form, write in the WHEN-NEW-ITEM-INSTANCE TRIGGER
at block level (if have more than one LOV)
IF :SYSTEM.MODE = 'ENTER-QUERY' THEN
IF get_item_property(:system.cursor_item,lov_name) IN ('YOUR
LOV1', 'LOV2' etc) THEN
IF SHOW_LOV(get_item_property(:system.cursor_item,lov_name))
THEN
NULL;
END IF;
END IF;
END IF;
The above code maybe tweak to suite your need and condition.
This way, we explicitly make the LOV appear in ENTER-QUERY mode
whenever the user clicks on an item with an attached LOV.
Hope this helps.
Mohammed R.Qurashi

Prevent interpretation of special characters in enter-query mode

My problem goes as follows:
- forms version: Forms [32 Bit] Version 6.0.8.10.3 (Production)
- non-database item block.X, char
- block.X is filled in post-query trigger. The post-query logic cannot be integrated in a view because it uses procedures, and usage of a pipelined function + view is currently not allowed due to "internal restrictions". Put simply: all logic to fill the field must remain in the post-query trigger
- user wants the field to be queryable. This is achieved by storing the entered criterium in a variable in the pre-query trigger, and using it in the post-query trigger to exclude records. E.g.
pre-query ==> help_block.query_X := block.X;
post-query ==> if help_block.query_X is not null and block.X is null or not block.X like help_block.query then raise form_trigger_failure; end if;
- this works fine for "regular" search strings. However:
- whenever the search string starts with <, <=, >, >=, !, forms seems to interpret the leading characters before doing anything else. During pre-query, block.X is null, and as soon as I use it in pl/sql, I get FRM-40831: Truncation Occured: value too long for field. E.g.
user puts the following in block.X ==> '<X', so he wants to search for records with value '<X' (text; not 'smaller than ...')
pre-query => msg.show(block.X) ==> appears to be empty/null, but right after the message, I get FRM-40831 Truncation Occured: value too long for field ...
This only happens if < is the first non-space character in the search string.
Does anyone know of a way to prevent oracle from interpreting the <, <=, ... characters entered in enter-query mode?

I'm sorry for not making myself clear; I'll give it another go:
The problem is that, if I enter '<abc' in a form field in enter-query mode (so during creation of the "example record"), forms immediately interprets the < as 'smaller than' and does some obscure things with it (my guess: converting to a where clause, but since I'm using a non db field, this actually does nothing), and finishes by erasing the field contents (in the example record). In the pre-query trigger, I can no longer get the '<abc' and store it. I want one of the following:
- prevent forms from interpreting the '<' in front (same thing happens for !=, <=, >=, =, ...)
or
- capture the entered string ('<abc') before forms reacts to the '<' in front
Edited by: [email protected] on Feb 17, 2009 12:30 PM

Initial Value in Enter Query Mode

Hi Everyone,
If you ever need to set a "visual" default (or initial) value for an item in Enter-Query mode, here is one solution to accomplish this:
Create a WHEN-NEW-ITEM-INSTANCE trigger at the block level where the item is located. Make sure it can fire in Enter-Query mode.
WHEN-NEW-ITEM-INSTANCE
If :system.mode = 'ENTER-QUERY' AND :system.cursor_item = <YourItemName> AND <YourItemName> IS NULL Then
<YourItemName> := <TheInitialValue>;
End If;You may wish to play with the "Keep Cursor Position" property of the item should you want the cursor to go back to the item position it was when the item was left.

It seems that your solution described solves my problem expressed 2 months ago....
I'll try it out....
Thanks......
Sim

KEY-CERREC TRIGGER IN ENTER-QUERY MODE

Similar Messages

Maybe you are looking for