LOV in query mode (calendar)

Hello,
i know it's possible to enter in query mode and then select a value for quwey from a LOV.
but in case of a Calendar (date_lov.get_date(...) ) i got that 'Undefined control key... press Ctrl+K for a list of all keys'. something like this
why the LOV does not appear in this case? get_date is a procedure, contained in DATE_LOV package
so what i want is to enter in query mode and then call the calendar to choose a date as search criteria
Thanks

hai,
Its not possible.
Because the date control is actually a seperate block, and in Query mode, we cannot more to a separate block.
Regards,
Manu.

Similar Messages

  • Showing LOV in query mode

    Hi
    How do you display a LOV using coding in a command button when the form is in query mode.

    do you mean enter-query-mode?

  • LOV in Query mode

    Hi,
    I have a form which when the user enters query mode, the user should be able to access the LOV attached to the 3 fields that are on the header level. On selection the values should be populated in the fields. The 3 fields are in a query only block.
    If I use Show lov, and i make a selection, i get an error message saying that you cannot insert records.
    Any thoughts ?
    Preeti

    hai,
    Its not possible.
    Because the date control is actually a seperate block, and in Query mode, we cannot more to a separate block.
    Regards,
    Manu.

  • LOV icon missing in query mode

    Hi,
    I'm using a LOV in query mode. But in Query mode the button with the 3 dots is missing. I can only enter the LOV by pressing CTRL+L. To improve the easy of use, I want to show the button in the text field (with LOV) as well. How can I realize this?
    Regards,
    Sten

    I've changed the registry.dat file which I found on the middle tier in the folder
    /u01/applmgr/rooscomn/java/oracle/forms/registry/
    but without the desired result. When I switch in a form to query mode, there is still no button in the textfield (3 dots).
    Thanks in advance!

  • [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

  • 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

  • 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.

  • Calendar in Enter-Query Mode

    Dear All ,
    i hv posted my problems before.
    My. Calendar does not work in Enter-Query Mode.
    It says 'Function Key Not Allowed' It's Because of the Code(Go_Block) in Get Date procedure in the date package.
    Any Suggestion on this will be highly appreciated.

    You will have to change the calendar code to reside in a separate Form and use CALL_FORM to pop it up. This will be valid in Enter-Query mode - You'll then pass the selection back in a Global variable.

  • LOV button in query mode

    Why is an LOV button not shown when the block is in enter-query mode, but there is still an LOV available (using F9 button)?

    This has already been filed as a Forms bug, no. 2179613 'EXTEND APP.UI.LOVBUTTONS TO ALLOW DISPLAY OF LOV IN ENTER-QUERY MODE'.
    "Currently the facility to display LOV buttons automatically - the setting app.ui.lovButtons=true in the registry.dat file only works in data entry mode. It would be useful to be able to display the generated button in Enter query mode as well."
    The priority is "Minor Error, No Loss of Service", so I doubt if this will be fixed soon.

  • 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.

  • LOV , EXECUTE-QUERY, ENTER-MODE ?

    when the form load , i execute a query. Then i want to choose from an lov
    a value and execute a query for a detail block, however, when i want to update
    the queried records, it doesn't work. The query mode has to be in enter mode.
    The question is how do we implement the enter mode logic into the lov
    button.
    Please explain how to do this in detail
    null

    <BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by candace stover ([email protected]):
    Hi -
    THANK YOU FOR YOUR REPLY
    I tried your code , but still does not put me in "enter query" mode to update or insert records on the detail block after your code is executed.
    I implemented this in a simple master detail of Dept/Emp. I implemented an LOV to select a JOB so that I would only see the employees within the department that have the JOB I select when I press the LOV button. The LOV returns its value into a parameter called "selected_job".
    Here is the code I put in my When-Button-Pressed trigger
    if show_lov('job_lov') then
    go_block('emp');
    set_block_property('emp', default_where, 'where job = ' | | '''' | | :parameter.selected_job | | '''');
    execute_query;
    -- set block property back so that all queries on this
    -- block do not have this criteria
    set_block_property('emp', default_where, '');
    else
    -- execute the default child query
    go_block('emp');
    set_block_property('emp', default_where, '');
    execute_query;
    end if;
    Hope this helps,
    Candace Stover
    Forms Product Management<HR></BLOCKQUOTE>
    null

  • What is the differences between viewCriteria query modes?

    Hello all,
    recently we faced a performance issue in a production application. after tracing  we found  that the issue was caused by setting the query mode of the view criteria to in memory.
    bussiness case description:
    when creating a new record for table A, I want to populate one field depending on records in another table B, so I used model driven LOV.
    The problem was that new records were created for both tables in the same ADF train i.e. the data for both tables were not posted or committed yet.
    so by using a query based ViewObject + viewCriteria with query mode set to memory for viewCriteria I managed to populate the LOV with the correct data,
    in another page I will show database records for table A with LOV to show meaningful messages to users ,  but I can as well create new records for table A ,but the loading of this page is very slow.
    tracing:
    using alter session set sql_trace=true; I found that table B is fully scanned and all rows are fetched-180000+ record-.
    Problem description:
    from the trace file generated found that the query issued did not have a where clause.
    also found that the viewObject fetched the entire table into memory- 180000+ record,-  then searched them in memory.
    Solution:
    changing the query mode of the viewCriteria seems to solve the issue
    so in order to avoid such issues in the future ,I wanted to make sure I understand the differences between the query modes of view criteria and their impact on the performance and if there are any differences if the viewObject is based on an entity or a sql dml.
    this is what I know so far -please correct me if I am mistaken-:
    1)database: search the database appending the conditions of the viewCriteria to whatever the query is
    2)memory: search the rows that are already in the memory.
    3)both: search both database and memory.
    also, in case I updated one of the records in the memory but did not yet post or commit will the fetched rows have the updated values? and if these changes fails the condition from the viewCriteria , will the rows be shown?.

    The camera roll contains all the photos and videos taken on your device, as well as any saved on your device from the internet, emails, text messages, etc.  The photo library contains photos synced to your device from your computer.
    Only camera roll photos are synced using iCloud with photo stream.  And photo stream only syncs photos, not videos.

  • Query mode of Master Detail Form

    I have a master-detail form.
    I'm passing parameters to that form to autoquery data.
    Everything works fine but "Next" button in a detail block.
    I'm getting:
    An unexpected error occurred: ORA-06502: PL/SQL: numeric or value error: NULL
    index table key value (WWV-16016).
    After autoquery LASTIN_SET variable of DEFAULT block is set "5" (number of rows in detail block).
    When I click on "Next" button LASTIN_SET variable is set to "0" instead of "5" and that causes a problem.
    So, somehow LASTIN_SET is not preserved between clicks.
    In fish_size_form master-detail form
    ... before displaying the page
    shrimp.p_set_parameter_fish_size(p_session,
    p_block_name,
    p_object_name,
    p_instance,
    p_event_type,
    p_user_args
    This is a code of shrimp.p_set_parameter_fish_size
    p_session in out nocopy portal92.wwa_api_module_session,
    p_block_name varchar2,
    p_object_name varchar2,
    p_instance varchar2,
    p_event_type varchar2,
    p_user_args varchar2
    is
    sess_store portal92.wwsto_api_session;
    status varchar2(80);
    station varchar2(80);
    date_time varchar2(80);
    sample varchar2(80);
    species_code varchar2(80);
    form_state varchar2(100);
    begin
    form_state := p_session.get_value_as_varchar2(
    p_block_name => 'MASTER_BLOCK',
    p_attribute_name => '_FORM_STATE');
    if form_state = 'QUERY_AND_SAVE' then
    sess_store := portal92.wwsto_api_session.load_session(
    p_domain => 'sfnrc',
    p_sub_domain => 'shrimp');
    status := sess_store.get_attribute_as_varchar2(p_name => 'status');
    if status = 'apply' then
    station := sess_store.get_attribute_as_varchar2(p_name => 'station');
    if station is not null then
    p_session.set_shadow_value(
    p_block_name => 'MASTER_BLOCK',
    p_attribute_name => 'A_O_S_M_O_STATION__ID_K',
    p_value => '='||station,
    p_language => portal92.wwctx_api.get_nls_language );
    end if;
    date_time := sess_store.get_attribute_as_varchar2(p_name => 'date_time');
    if date_time is not null then
    p_session.set_shadow_value(
    p_block_name => 'MASTER_BLOCK',
    p_attribute_name => 'A_O_IN__SAMPLE_IN__DATE_TIME_K',
    p_value => '='||to_char(to_date(date_time,'yyyy/mm/dd hh24mi'),'yyyy/mm/dd hh24:mi'),
    p_language => portal92.wwctx_api.get_nls_language);
    end if;
    sample := sess_store.get_attribute_as_varchar2(p_name => 'sample');
    if sample is not null then
    p_session.set_shadow_value(
    p_block_name => 'MASTER_BLOCK',
    p_attribute_name => 'A_OBSERVED_IN__SAMPLE_NUMBER_K',
    p_value => '='||sample,
    p_language => portal92.wwctx_api.get_nls_language);
    end if;
    species_code := sess_store.get_attribute_as_varchar2(p_name => 'species_code');
    p_session.set_shadow_value(
    p_block_name => 'MASTER_BLOCK',
    p_attribute_name => 'A_S_I_PROJECT_SPECIES_CODE_K',
    p_value => '='||species_code,
    p_language => portal92.wwctx_api.get_nls_language );
    sess_store.set_attribute(p_name => 'status',p_value => 'done');
    sess_store.save_session;
    p_session.save_session;
    fish_size_form.wwv_master_gensys_1(
    p_block_name => p_block_name,
    p_object_name => p_object_name,
    p_instance => p_instance,
    p_event_type => p_event_type,
    p_user_args => p_user_args,
    p_session => p_session );
    end if;
    end if;
    end;
    What I'm missing here.
    Aantoliy.

    Say, I click on Update Push button. This will invoke a LOV that will occurs 5 times and then display the header and detail record.
    Even if, I am able to get the records in the canvas, I am not able to update the records of the master. The record_status is in INSERT mode of the header block. Interestingly, if i click 2nd time on update button and then get the records after executing LOV, the query enters the query mode and I am able to update the records then.
    Please suggest how to overcome the problem on a sigle click on UPDATE button.

  • 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

Maybe you are looking for