Analytics Software

Change LOV property Automatic Skip to NO.

Regards

Dear Matthew,

Yes I have done the same, but still it is jumping to next column.

Please help me

Thanks,

Please some advise,

Thanks

Are there any triggers on the item with lov?

no sir, nothing is there

Forms version?

version is 10g

No reply from any one, please suggest me some idea.

Dear,

without knowing the code, no one can help. How you are populating the LOV? what are the codes written in the KEY-LISTVAL triggers in item level, block level and form level?

Manu.

I dont have any tiggers for that item or block level, i have only LOV to the item.

Dear,

Then can you post the properties of that item and LOV?

Manu.

This all the LOV and item property palette.

Thanks,

I notice you are using popup menus which I have only used one time.  Is there logic in the POPUP popup menu that could be causing this problem?  Maybe remove it from the property palette and try running the form again just to see if it behaves the same way.

Also, you don't show your form-level triggers.  Could there be a pre-text, post-text, when-new-item-instance, etc... trigger causing this behavior?

Check Field level triggers like key-next-item or when validate item - if you have dont have then check block level. somewhere your trigger/code is telling to move next field. also best way to find references made to this field, so find all pl/sql with this field name and check...

No tiggers is there, it's a simple form,

This is only a guess as your text on the image says: "When I select one of these and Enter, the cursor is going to the next column..."

You may be encountering the behaviour for the default key mapping of Enter.

https://docs.oracle.com/middleware/1221/formsandreports/deploy-forms/configure.htm#CACCGDGF

By default, whether deploying client/server or over the Web pressing the ENTER key takes the cursor to the next navigable item in the block. To override this default behavior it is necessary to modify the forms resource file to revise the key mapping details.

Modify fmrweb.res and change the Forms Function Number (FFN) from 27 to 75 for the Return Key. The line should be changed to the following:

10 : 0 : "Return" : 75 : "Return" 

By default, the line is displayed with an FFN of 27 and looks as follows:

10 : 0 : "Return" : 27 : "Return" 

This line should NOT fire the Key-Enter trigger since the Return or Enter key is actually returning the Return function represented by the FFN of 27. The FFN of 75 represents the Enter function and fires the Key-Enter trigger.

Set the property 'Automatic Skip' to no for both the text item and LOV.