Push button in enter_query mode

Hi all !
I've got the following Problem in Forms 4.5:
When i enter the query mode with "enter_query",
i cant push any other (user defined) button i have placed on the form (other Blocks). Thats my problem....
It seems, that my buttons have to belong to the "Query-Block" (because if so-it works).
But i have got some other forms sources - and in these forms the buttons DONT belong to the Query-Block and i CAN push the Buttons in ENTER_QUERY - Mode.
Please, can somebody can give me e hint .... ??

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 :) )

Similar Messages

  • Enabling a push button in query mode only

    Hello!!
    How do you enable a push button only in query mode? Do I need to write some code? If so can anybody help?

    Use the following code
    if :system.mode = 'ENTER-QUERY' THEN
    SET_ITEM_PROPERTY('BUTTON',ENABLE,PROPERTY_TRUE);
    ELSE
    SET_ITEM_PROPERTY('BUTTON',ENABLE,PROPERTY_FALSE);
    END IF;

  • Enable push button

    Hi,
       I need to customize an infotype. I've created one push button on the screen, when click on the button, a table control will show out.
      However, I don't know why when I display the screen in PA30, the push button show disabled mode and I couldn't click on it.
      Do anyone know why and how can I solve it?
      Many thanks in advance.

    in the lay out check tha attributes of thatbutton.check the display tab i the attributes.in that check box corresponiding to invisible should not be checked(empty).
    regards,
    bharat.

  • Open a form in enter_query mode

    Qs no:1:- I want to open a form in enter_query mode.
    Qs no:2 :- after they query 4 fields(blk1) ...depending on that the rest of the informative part of that form(blk2) gets populated.
    Now user hit OK (push button).
    Now all the fields should be blanked including those 4 fields and the informative part and the form should stay at enter_query mode.
    FYI:- There is no master-detail relation between two blocks.blk2 gets populated when user puts data in the 4th field and press tab ...
    I have written the code to populate the informative part in when-validate-trigger of the 4th text field.
    How can I do that?
    please suggest..
    Edited by: 977083 on May 13, 2013 4:59 AM

    Hello,
    Switch to enter query mode at the end of the When-New-Form-Instance trigger:
    Go_Block('the_block_to_query');
    do_key('enter_query');Francois

  • How to Enable a Push Button In The Form That Is Always Greyed Out?

    Greetings All,
    I am trying to enable an existing "Return" Push Button(PB) which is always greyed out whenever the form is called in either an update or review mode. After some research, I found that this PB's functional property is "Enabled" (i.e. the enabled value = 'Yes'), and it is coded programatically set 'Off' in 30 places and 'On' in 2 places in the form that I inherit from my predecessor by using the following code:
    SET_ITEM_ON_OR_OFF('BLK_UPDATE.PB_RETURN', <XXXXX>);
    Where <XXXXX> could be either TRUE or FALSE. I've been spending a lot of time in trying to enable this "Return" PB (without modifying the existing programming code) by adding the 'SET_ITEM_ON_OR_OFF' built-in command to set the PB on in WHEN-BUTTON-PRESSED TRIGGER for the PB_RETURN and WHEN-NEW-FORM-INSTANCE Trigger, but all tries in vain. Could you please help me with the following question?
    What is the easiest way to enable a PB that is set programmatically?
    Is there something else I should know to enable a PB, in addition to what I have already mentioned above?
    Thanks in advance,
    Jinlan
    --

    Thanks all for your information and help. I included the following code, as suggested by Manu, in WHEN-MOUSE-DOWN TRIGGER for the PB_RETURN and WHEN-NEW-FORM-INSTANCE TRIGGER:
    SET_ITEM_PROPERTY ('BLK_UPDATE.PB_RETURN_WORK_REQ', ENABLED, PROPERTY_TRUE);
    and I made sure there was no " SET_ITEM_ON_OR_OFF('BLK_UPDATE.PB_RETURN_WORK_REQ', FALSE);" statements after the above code, but, the "Return" PB is still in grey; in other words, it is still not accessible when my form is called.
    Perhaps, I need to place the above SET_ITEM_PROPERTY code in a different trigger other than the triggers mentioned above, uh? Any thoughts on this?
    Manu,
    You are absolutely right that the "SET_ITEM_ON_OR_OFF" is an ih-house written procedure which is defined/stored in the Attached Libraries. (I should have checked before making the "built-in" assumption. Thanks for catching and clarifying this.) Please help me with the following questions:
    How do I view the procedure in the Attached Libraries???
    Thanks in advance,
    Jinlan
    --

  • 'Create' Push button is not working in BDC and LSMW while uploading G/L master data

    Hello Experts:
    I am facing the following problem:
    While uploading G/L master data with the BDC program, 'create' push button is not working  even after executing following lines.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=ACC_CRE'.
    Create G/L account  screen is not coming in BDC. Please suggest me what to do.
    Thanks !!

    Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
    Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
    Hi Glen Anthony
    Thank you for the reply Glen Anthony please take a look at the following code.
    REPORT  ZFI_BDC_FS00
            NO STANDARD PAGE HEADING LINE-SIZE 255.
    *INCLUDE BDCRECX1.
    TYPES : BEGIN OF STR,
       BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS,        "Company Code
       SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR,        "G/L Account Number
       KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS,        "G/L Account Group
       XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT,    "P&L statement account
       XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK,        "Indicator: Account is a balance sheet account?
       TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML,  "G/L account short text
       TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML,  "G/L account short text
       WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS,      "Account currency
       XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH,      "Indicator: Only Manage Balances in Local Currency
       MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ,      "Tax Category in Account Master Record
       XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO,      "Indicator: Tax code is not a required field
       MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ,      "Account is reconciliation account
       XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW,      "Indicator: Open item management?
       XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES,      "Indicator: Can Line Items Be Displayed by Account?
       ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA,      "Key for sorting according to assignment numbers
       FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG,      "Field status group
       XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB,      "Indicator: Is account only posted to automatically?
       END OF STR.
    DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
            IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
            TXT(4096) TYPE C OCCURS 0,
            MSG TYPE STRING,
            COUNT(5) TYPE N.
    SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
       PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
    SELECTION-SCREEN : END OF BLOCK B1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
    CALL FUNCTION 'F4_FILENAME'
      EXPORTING
        PROGRAM_NAME        = SYST-CPROG
        DYNPRO_NUMBER       = SYST-DYNNR
    *   FIELD_NAME          = ' '
      IMPORTING
        FILE_NAME           = MY_FILE
    CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
       EXPORTING
    *   I_FIELD_SEPERATOR          =
    *   I_LINE_HEADER              =
         I_TAB_RAW_DATA             = TXT
         I_FILENAME                 = MY_FILE
       TABLES
         I_TAB_CONVERTED_DATA       = ITAB[]
      EXCEPTIONS
        CONVERSION_FAILED          = 1
        OTHERS                     = 2
    IF SY-SUBRC <> 0.
    * IMPLEMENT SUITABLE ERROR HANDLING HERE
    ENDIF.
    START-OF-SELECTION.
    COUNT = 0.
    LOOP AT ITAB.
    *PERFORM OPEN_GROUP.
    REFRESH  IT_BDCDATA.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_KEY-BUKRS'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=ACC_CRE'.
    *PERFORM BDC_FIELD       USING 'BDC_CURSOR'
    *                              'GLACCOUNT_SCREEN_KEY-BUKRS'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                                   ITAB-SAKNR. "'5'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
                                   ITAB-BUKRS. "'TATA'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=2102_GROUP'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_COA-KTOKS'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   ITAB-KTOKS. "'GL'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   ITAB-XPLACCT. "'X'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=2102_BS_PL'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_COA-XBILK'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   ITAB-KTOKS. "'GL'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                                   ITAB-XPLACCT. "''.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                   ITAB-XBILK. "'X'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=TAB02'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                                   ITAB-KTOKS. "'GL'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                                   ITAB-XBILK. "'X'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_COA-TXT50_ML'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                                   ITAB-TXT20_ML. "'G/L ACCOUNT'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                                   ITAB-TXT50_ML. "'G/L ACCOUNT'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=TAB03'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                                   ITAB-WAERS. "'INR'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
                                   ITAB-XSALH. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                                   ITAB-MWSKZ. "'*'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
                                   ITAB-XMWNO. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                                   ITAB-MITKZ. "''.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                                   ITAB-XOPVW. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                                   ITAB-XKRES. "'X'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                                   ITAB-ZUAWA. "'1'.
    PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
    PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                                   '=SAVE'.
    PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                                   'GLACCOUNT_SCREEN_CCODE-XINTB'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                                   ITAB-FSTAG. "'G019'.
    PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                                   ITAB-XINTB. "'X'.
    *PERFORM BDC_TRANSACTION USING 'FS00'.
    CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
    COUNT = COUNT + 1.
    *PERFORM CLOSE_GROUP.
    ENDLOOP.
    CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
    MESSAGE MSG TYPE 'I'.
    FORM BDC_DYNPRO USING PROGRAM DYNPRO.
       CLEAR IT_BDCDATA.
       IT_BDCDATA-PROGRAM  = PROGRAM.
       IT_BDCDATA-DYNPRO   = DYNPRO.
       IT_BDCDATA-DYNBEGIN = 'X'.
       APPEND IT_BDCDATA.
    ENDFORM.
    *        INSERT FIELD                                                  *
    FORM BDC_FIELD USING FNAM FVAL.
    *  IF FVAL <> NODATA.
         CLEAR IT_BDCDATA.
         IT_BDCDATA-FNAM = FNAM.
         IT_BDCDATA-FVAL = FVAL.
         APPEND IT_BDCDATA.
    *  ENDIF.
    ENDFORM.

  • Push buttons not appearing

    Hello Experts,
    I had made push buttons on my screen through layout editor and set property as invisible (By Checking Invisible checkbox).
    Now, based on some conditions at run time I want those push buttons to appear on screen.
    For this I had written following code:
    if sy-dynnr = 0101.
      loop at screen.
        if screen-name = 'CUNDFILTER'.
          screen-active = 1.
          screen-invisible = 0.
          elseif screen-name = 'CFILTER'.
            screen-active = 1.
            screen-invisible = 0.
            ELSEIF screen-name = 'DSELALL'.
              screen-active = 1.
              screen-invisible = 0.
              elseif screen-name = 'SELECTALL'.
              screen-active = 1.
              screen-invisible = 0.
         endif.
         modify screen.
       endloop.
       endif.
    I had checked in debug mode, above lines are getting executed but push buttons are not appearing on the screen at runtime.
    Please help.

    Hi,
    You have to code your LOOP AT SCREEN in the PBO...
    Kr,
    Manu.

  • Prob with Push Buttons in the selection screen

    Hi All,
    1) I have 6 push buttons in the selection screen(Normal Report), 3 in a first row(P11, P12, P13) and 3 in the second row(P21, P22, P23). If I press one push button(for ex P11) the other two Push buttons(P12 P13) should grey out(Inactive mode). If I press P22, P21 & P23 shoul grey out.
    2) I need color change for the Inactive push buttons.
    Thanks
    Kris

    Can you please post your selection screen definition? I don't understand what you want to achieve by greying out the other pushbuttons when one is pressed.
    Does that mean pushing one button will do nothing except greying out the buttons?
    Typically when you push a button, you want to continue to execute the required processing for that button not just grey out other pushbuttons and stay in the selection screen.
    Anyway, you can achieve that using the following logic. I am not sure how and if you can achieve the color change.
    TABLES: sscrfields.
    DATA: v_button_pushed(5).
    SELECTION-SCREEN PUSHBUTTON /1(10) p11 USER-COMMAND push1.
    SELECTION-SCREEN PUSHBUTTON 12(10) p12 USER-COMMAND push2.
    SELECTION-SCREEN PUSHBUTTON 23(10) p13 USER-COMMAND push3.
    SELECTION-SCREEN PUSHBUTTON /1(10) p21 USER-COMMAND push4.
    SELECTION-SCREEN PUSHBUTTON 12(10) p22 USER-COMMAND push5.
    SELECTION-SCREEN PUSHBUTTON 23(10) p23 USER-COMMAND push6.
    INITIALIZATION.
      p11 = 'Push11'.
      p12 = 'Push12'.
      p13 = 'Push13'.
      p21 = 'Push21'.
      p22 = 'Push22'.
      p23 = 'Push23'.
    AT SELECTION-SCREEN OUTPUT.
      CASE v_button_pushed.
        WHEN 'PUSH1'.
          LOOP AT SCREEN.
            CHECK screen-name <> 'P11'.
            screen-input = 0.
            MODIFY SCREEN.
          ENDLOOP.
        WHEN 'PUSH2'.
        WHEN 'PUSH3'.
        WHEN 'PUSH4'.
        WHEN 'PUSH5'.
        WHEN 'PUSH6'.
        WHEN OTHERS.
      ENDCASE.
    AT SELECTION-SCREEN.
      v_button_pushed = sscrfields-ucomm.

  • How to edit a particular row in the table ctrl when a push button is clickd

    Hi Experts,
    How to edit a particular row (except the Primary keys) after selecting it in the TABLE CONTROL when a
    push button is clicked in the table control.
    For Eg. If you have a push button say "Modify", the particular row what we select in the table control should be in a
    editable mode after clicking "Modify" Push button.
    Please help me out.
    Thanks in advance.

    Hey Ram,
    Thanks a ton.
    Its working fine...sorry for the late reply.
    The reason behind the delay is because i had modified my code as per your logic it worked fine but the thing is that the whole column was in editable mode but not a single row.
    For E.g  If i want to edit a particular row, first i select the row and then  click on "Modify" button. After i click on the button, the whole column gets in a editable mode including the one which i intentionally selected.
    Here, the solution is that you have to set a flag in PBO so that once it is done with PBO then it need not come back again after we click on "Modify" button.
    And one more query is that after you modify a particular row in the table control ( When it is in editable mode) and click on the "Save" button, it is not getting updated to database.
    To update the database, we need to select the row once again after modifying it and click on the "Save" button.
    Here, database is updating only when it is selected again. If it is not selected, it is not getting updated.
    If you have any alternative solution, then please help me out.( I hope i am clear with the question.)
    Thanks,
    Ananth.

  • SHOW LOV IN ENTER_QUERY MODE BY USING WHEN_BUTTON_PRESSED TRIGGER

    HI ALL...
    I HAVE A CANDIDATE BLOCK. IN ENTER QUERY MODE BY PRESSING f9 KEY I AM ABLE TO SEE
    THE LOV BUT WHEN PRESSING THE PUSH BUTTON ITS NOT COMING
    BY USING SHOW_LOV BUILT IN..
    PLEASE HELP ME..
    ASAP

    Ok..The key navigable and mouse navigable properties of buttons were yes.
    Thats why it was not working ..now its working by changing it..any way thanks a lot.
    Thanks
    Sam......

  • Create_record in enter_query mode

    Dear members,
    (Forms 6i c/s)
    In enter_query mode, when the user wants to create a new record, I'd like to exit from the mode and create the record.
    But "create_record" (F6) is not allowed in this mode, so it doesn't get to the key-crerec trigger. Thus I can't find a place to put my "exit_form / create_record" code.
    Any idea ?

    Unfortunately, a lot of triggers ignore the "Fire in Enter-Query Mode" property, and apparently you have stumbled into one of them. Forms was written by humans and they make mistakes -- someone probably decided that no matter what, since you couldn't create a new record legally in Enter-Query mode, that they should disable the key-trigger. Too bad.
    I tried to get the Key-Crerec trigger to work here and had no luck. I'm afraid you're going to have to try a button and When-button-pressed trigger.

  • Motion assistant push button

    Hi,
    I am using Motion Assistant software and labview to control step motors. There is no problem about controlling the motors via Motion Assistant but I want to design a Graphical User Interface in order to control the motors via push buttons in labview. I have designed a GUI with labview (which is in the attachment). I want my motor to run at the input speed rate while the button is pressed and stop while the button is unpressed. But this algorithm doesn't allow this application. It stops and goes on running I don't want it to stop. I want it to run continuously.
    Do you have any suggestions about this application?
    Attachments:
    pushbutton.vi ‏15 KB

    Why don't you use the velocity mode ?
    Attached is a basic template showing how I would do this.
    Attachments:
    Control motor template (LV2012).vi ‏19 KB

  • Missing Push Buttons in Pie Chart

    The above pie chart is in the development mode, where there is no push buttons in the canvas...like 2014,2013,2012,2011,2010
    Here when the same pie chart is taken in preview mode, there appears push buttons to select the year and find the respective cast numer in respective year, i could not find any option in the properties of pie chart.....Would be thankful if someone can plz clarify me..
    Thanks and Regards
    Ranendra

    You can not see it in the canvas because it is checked as hidden in the object browser. If you want to display this in design time, uncheck the hide option.

  • How do I use a push button digital trigger with my 6034E DAQ board?

    I am only a Lab View toddler.
    I am currently using a push button, wired to PFIO/TRIG1 and DGND, with a anolog trigger. However noise is causing my program to be triggered. I was told that a digital trigger would help to reduce the random triggering. How do I create a push button digital trigger?
    Thanks

    implement a schmitt trigger.
    Struggling with Labview wrote in message
    <[email protected]>...
    >I am only a Lab View toddler.
    >I am currently using a push button, wired to PFIO/TRIG1 and DGND, with
    >a anolog trigger. However noise is causing my program to be triggered.
    >I was told that a digital trigger would help to reduce the random
    >triggering. How do I create a push button digital trigger?
    >Thanks

  • Push button query!!!!!!! help needed

    hello all,
    I HAVE USED THIS LOGIC FOR MAKING THE DATA ASCENDING AND
    DESECENDING,AND TRIED ALL THE
    SOLUTIONS THAT WERE SUPPLIED BY MY FRIENDS IN THIS GROUP,BUT COULD NOT
    CHANGE THE
    VISUAL ATTRIBUTE OF THE BUTTON.I AM REPEATING MY QUERY.I WANT TO HAVE
    THE
    PUSH BUTTON TO SIGNIFY VISUALLY THE ASCENDING AND DESCENDING DATA I.E
    WHEN THE
    DATA COMES IN THE ASCENDING WAY,THE PUSH BUTTON
    SHOULD HAVE A "inverted v"ACC CODE"" ALONG WITH NAME "ACC CODE" I.E IT SHOULD
    LOOK LIKE "ACC CODE "ACC CODE inverted v "
    AND WHEN THE DATA COMES IN THE DESCENDING WAY,THE PUSH BUTTON
    SHOULD HAVE A " v".I.E IT SHOULD
    LOOK LIKE "ACC CODE "ACC CODE' v' ".SO PLZ HELP me TO GET THIS .
    Any changes should be made to nls_lang parameter in registry???????????
    PLZ LET ME KNOW WHAT IS FONT THAT I SHOULD USE.U CAN CHANGE THE CODING
    THAT I HAVE WRITTEN
    IN THE "WHEN BUTTON PRESSED" TRIGGER OF ACC_CODE.
    BEGIN
    go_block('age_tran');
    BEGIN
    IF
    get_item_property('PB_ACC_ORDER',LABEL)='&Acc Code' THEN
    set_block_property('age_tran',order_by,'acc_code ASC');
    execute_query(no_validate);
    SET_ITEM_PROPERTY('PB_ACC_ORDER',LABEL,'&Acc Code'||'
    '||upper(chr(94)));
    ElSIF
    get_item_property('pb_acc_order',LABEL)='&Acc Code'||'
    '||upper(chr(94)) THEN
    Set_block_property('age_tran',order_by,' acc_code DESC');
    execute_query(no_validate);
    SET_ITEM_PROPERTY('pb_acc_order',LABEL,'&Acc Code'||' '||'v');
    ELSE
    Set_block_property('age_tran',order_by,'BALANCE DESC');
    execute_query(no_validate);
    SET_ITEM_PROPERTY('pb_acc_order',LABEL,'&Acc Code');
    END IF;
    END;
    END;
    THANKING U

    Hi Shiju,
    U can use the combination of fornt slash(/) and back slash(\) to fulfil ur requirement.
    For ascending u can use /\ and for descending u can use \/. Does this solve the purpose?
    I think it will.
    Suprabhat.

Maybe you are looking for