LOV button in enter query mode

Hi
How do I show LOV button(Forms 9.0.2) in enter query mode?As of now LOV button is displayed only in the create mode.
Binod.

Hi Andrew,
Thanx for the reply. Actually I have not associated any trigger for this. Here Im refering the LOV button which comes inside the respective field(I mean we change the property lov_button to 'true in the regitry.dat). This button is not getting displayed in the enter query mode.
I hope now you are clear with the query.
Binod.

Similar Messages

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

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

[Solved] Problem with LOV and 'enter query' mode

Hi all,
I'm kind of new to Forms and I'm having some problems that I'm not being able to resolve. I already search it on the net, but nothing relevant came up. If anyone could help me I appreciated it.
In my form I have some fields, and in one of them I have a LOV, and almost everything works fine. I inserted data, changed it, deleted it and all it's ok.
But when I change to 'enter query' mode, when I try to search for data on the LOV field it ignores what I write.
That is, for it, it's the same if I make F11 -> write 'aaaa' -> ctrl + F11 or if I make F11 -> '%' -> ctrl + F11.
It behaves the same way, shows me all the records.
Probably I'm missing something basic, but I'm not getting it...
Thanks,
Ana

when you create a lov by wizard the lov and record group have always the same name..
the problem is that the item is NOT based in the tabe.
what kind of query do you execute if you choose something from a love which is not based on the db?
i mean, this item has no influence on the query of the table, so whatever you choose it's like a "select * from table"
i hope i was clear

Starting form in Enter-Query mode disables some buttons on Smartbar

Whenn I run a form (on the Web) which starts in Enter-Query mode, the buttons "Execute Query" and "Enter Query" are disabled on the Smartbar. Also the corresponding menu options are disabled. Besides, it is psossible to use the appropiate keys (in my case: F7 and F8).
Has anyone experienced the same problem and is there a solution?
Let me know.
Thanx

Frank: Thats what i thought too -but i saw (in other Sources) that it could be done, but how..
Eugeniy I Duzhinskiy:
So, many Thanks to you. It works fine !!!!
(Its great to see there are some other Forms Users out there :) )

Change background color in enter-query mode

Hi everyone,
I am trying to Change background color in enter-query mode in forms10g. I am using this
Set_Item_property('org.branch_code', BACKGROUND_COLOR, 'Green' );
Thanks

This is the code that allows to colorise items in enter_query mode, then de-colorize them after execute_query.
Assume that you have created a VA_QUERY visual atribute in your module.
-- Colorise in enter-query mode --
PROCEDURE Start_query IS
LC$Block      Varchar2(30) := Name_in('system.trigger_block') ;
LC$item       varchar2(60);
LC$itemdeb    varchar2(60);
LN$len        pls_integer ;
BEGIN
lc$itemdeb := get_block_property(LC$BLOCK, FIRST_ITEM) ;
lc$item := LC$BLOCK || '.' || lc$itemdeb ;
while lc$itemdeb is not null Loop
    IF GET_ITEM_PROPERTY(LC$Item , ITEM_TYPE) NOT IN ('BUTTON','RADIO GROUP','DISPLAY ITEM') Then
      IF GET_ITEM_PROPERTY(LC$Item , QUERYABLE ) = 'TRUE' Then
        set_item_property(LC$item, CURRENT_RECORD_ATTRIBUTE, 'VA_QUERY');
      End if ;
    End if ;
    lc$itemdeb := get_item_property( lc$item, NEXT_NAVIGATION_ITEM );
    lc$item := LC$BLOCK || '.' || lc$itemdeb ;
end loop ;
END;
-- Unclororize after execute_query --
PROCEDURE End_query IS
LC$Block     Varchar2(30) := Name_in('system.trigger_block') ;
LC$item     varchar2(60);
LC$itemdeb     varchar2(60);
LN$len          pls_integer ;
LN$Multi pls_integer ;
BEGIN
lc$itemdeb := get_block_property(LC$BLOCK, FIRST_ITEM) ;
lc$item := LC$BLOCK || '.' || lc$itemdeb ;
LN$Multi := GET_BLOCK_PROPERTY(LC$Block , RECORDS_DISPLAYED ) ;
while lc$itemdeb is not null Loop
    IF GET_ITEM_PROPERTY(LC$Item , ITEM_TYPE) NOT IN ('BUTTON','RADIO GROUP','DISPLAY ITEM') Then
      IF GET_ITEM_PROPERTY(LC$Item , QUERYABLE ) = 'TRUE' Then
         If LN$Multi > 1 Then
            set_item_property(LC$item, CURRENT_RECORD_ATTRIBUTE, 'VA_CURRENT_RECORD');
         Else
            set_item_property(LC$item, CURRENT_RECORD_ATTRIBUTE, '');
         End if ;
      End if ;
    End if ;
    lc$itemdeb := get_item_property( lc$item, NEXT_NAVIGATION_ITEM );
    lc$item := LC$BLOCK || '.' || lc$itemdeb ;
end loop ;
END;Francois

Changing visual attribute in Enter Query mode

Hello, I want to change visual attribute of all items in the first record when the user presses button for Enter_Query. I want that the user sees that the form is in enter query mode and it "waits" for the input of criteria. My code (copied from Help and modified) in trigger WHEN_BUTTON_PRESSED:
DECLARE
cur_itm VARCHAR2(80);
cur_block VARCHAR2(80);
BEGIN
ENTER_QUERY;
cur_block := :System.Cursor_Block;
cur_itm := Get_Block_Property( cur_block, FIRST_ITEM );
WHILE ( cur_itm IS NOT NULL ) LOOP
cur_itm := cur_block||'.'||cur_itm;
Set_Item_Instance_Property( cur_itm, CURRENT_RECORD, VISUAL_ATTRIBUTE,'yellow');
cur_itm := Get_Item_Property( cur_itm, NEXTITEM );
END LOOP;
END;
where yellow is the name of my visual attribute.
The problem is that I need to press the button TWICE to color the record.
Can anybody help me with this problem?
Natasa

(Wrong forum).
The problem is that enter_query stops executing your procedure until
another action ist started by the user.
You must create a short-time timer before issuing enter_query and set
your colour scheme in the when-timer-expired-trigger.

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.

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.

Disableing an item in enter query mode

Hello experts,
i want that a perticular item will be disabled after you press enter button of query menu.(or query->enter).Can any body please tell me what is the actual trigger in which i write the disable statement.
set_item_property('itemname', enabled, property_false);
Regards
Anutosh

You can't set the enabled property if the cursor is in the item and I expect it's the same for the query_allowed property. if the cursor is in the item which you set to Query_Allowed=false and then you go to enter-query mode, perhaps forms doesn't know what item to move the cursor to, so just leaves it where it is.
You can solve the problem by moving to a different item (with go_item) before setting the property.
When do you need to set the item back to enabled? If you want it enabled at all times other than when a query is being entered then use the Property Pallet to set the Query Allowed property. If you want to disable the field under certain conditions then the when-new-record-instance trigger might be better for you. Eg
if :system.mode = 'ENTER-QUERY' and <condition> then
go_item(<another item>);
set_item_property(<item>, enabled, property_false);
else
set_item_property(<item>, enabled, property_true);
set_item_property(<item>, update_allowed, property_true);
set_item_property(<item>, navigable, property_true);
set_item_property(<item>, update_null, property_true);
end if;It might be better to set the query_allowed property instead of the enabled property, but I can't check right now whether that's possible after the enter-query mode has begun.
The update_allowed, update_null and navigable properties are all set to false as a consequence of the enabled property being set to false. If they should be true then you need to reset them after reenabling the item.

Using Enter-Query Mode Programmatically

A question was raised in an earlier thread
QUERY CRITERIA MANAGER
about how to use Enter-Query mode programmatically in a way that doesn't stop
and prompt the user to enter a query after switching from Normal mode to Enter-Query mode.
Since the solution may not be widely known, I thought I'd demonstrate the technique here in a new thread.
Create a simple form with just two blocks. Using the data block wizard, create an EMP block with one
text item for ENAME. Place it on the canvas. Create the other block as a control block and name it CONTROL.
Inside the control block create the following items:
- create a text item named TXT_BOX
(The user will enter their search pattern criteria in this text box while in Normal mode.)
- create a push button item named EXECUTE_QUERY
(This button will switch to Enter-Query mode, execute the query, then return to Normal mode.)
Place both control items on the canvas.
Inside the WHEN-BUTTON-PRESSED trigger for the EXECUTE_QUERY button, enter the following code:
DECLARE
     timer_id TIMER;
BEGIN
     :GLOBAL.search_criteria := :CONTROL.TXT_BOX;
     GO_BLOCK('EMP');
     timer_id := CREATE_TIMER('ENT_QRY', 1500, NO_REPEAT);
     -- 1500 may be a little long, but provides a margin of error
     ENTER_QUERY;
END;
Next, create a WHEN-TIMER-EXPIRED trigger at the form level. Inside this trigger enter the following code:
If GET_APPLICATION_PROPERTY(TIMER_NAME) = 'ENT_QRY' THEN
     :EMP.ENAME := :GLOBAL.search_criteria;
     EXECUTE_QUERY;
     IF :SYSTEM.MODE = 'ENTER-QUERY' THEN
          EXIT_FORM; -- return to Normal mode
     END IF;
END IF;
GO_ITEM('CONTROL.TXT_BOX');
Now, when the user runs the form and logs into the SCOTT schema, he enters a search criteria
such as A% in the TXT_BOX while in Normal mode. Then clicks the EXECUTE_QUERY button.
The form will switch to Enter-Query mode, retrieve all names in ENAME that begin with the letter A,
and then return to Normal mode without pausing for the user to enter a search criteria.
If the query should happen to fail, the form displays the error:
"FRM-40301: Query caused no records to be retrieved. Re-enter."
then switches automatically back to Normal mode so the user can try entering a new criteria.

I'm showing how to do it when switching modes. I'm
not suggesting this is the best way to do a query.We need to look at this in the context of the original probelm in the thread linked to above. For most cases the when-timer-expired etc is just a huge detour around using the pre-query trigger but it's an interesting approach to the specific problem in the earlier thread. The OP there wanted to be able to type '>5000' into a number field in a non-database block, which we can do in a database block in enter-query mode, and use it as a query parameter in the database block. Perhaps if we enter this into a character field in the non-database block and populate the numeric field in the database block whilst in enter-query mode then we can do searches on ranges of data? Unfortunately it doesn't work - you get an ora-06502 error just like you do when using the pre-query trigger. For the situation in the original thread you would have to use a 'default where'.

Calendar enter query mode problem

I have successfully implemented the calendar utility supplied by
the demo.
However, has anyone figured out how to use it when in
enter-query mode? It doesn't work because you can't navigate
out of current block when in enter_query mode.

In your Exit button's WBP trigger, do this:If :System.mode = 'ENTER-QUERY' then
Exit_Form;
End if;
Exit_Form(No_Validate);To get the button to work while the form is in enter-query mode, it must be in the same block as the one being queried, or else you must set its Mouse Navigate property to No.

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;

Enter Query mode to Normal Mode

In my form i have a modify button. After clicking the modify mode, the mode will be enter-query. I have a number field. After entering the number i will be prompting the user to select yes or no from an alert. If he is selecting yes i will execute query modify save.. no problem.
If he is select no.. i am populating the values from a procedure.. i want to insert a new record.. but now i want to change the enter query mode.. how do that...
If i am using Exit_form; the populated details are getting cleared..
please help me..

Hi,
Try using Abort_query. Hope it will help you.
Regards
Gaurav Thakur

LOV button in enter query mode

Similar Messages

Maybe you are looking for