• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3980
  • Last Modified:

FRM-92100 and java.lang.StringIndexOutOfBoundsException when using Forms Built-in Edit_TextItem

We recently upgraded from Forms and Reports 6i to 10g.

We've found that when our users attempt to modify a field using the built-in editor (called with Edit_TextItem) they sometimes recieve an error message.  It seems to only happen if they open the text editor on a field which already contains data, modify the data, and then close the editor.  If they cut out the data and paste it right back in before making their edits, everything works fine.

FRM-92100: Your Connection to the Server was interrupted.
This may be the result of a network error, or a failure on the Server.
You will need to reestablish you connection.

Java EXception:
java.lang.StringIndexOutOfBoundsException: String index out of range: 471
      at java.lang.String.substring(Unknown Source)
      at oracle.ewt.lwAWT.lwText.LWTextField.scrollSelectionIntoView(Unknown Source)
      at oracle.ewt.lwAWT.lwText.LWTextComponent.select(Unknown Source)
      at oracle.ewt.lwAWT.lwText.LWTextComponent.select(Unknown Source)
      at oracle.ewt.lwAWT.lwText.LWTextComponent.setCaretPosition(Unknown Source)
      at oracle.ewt.lwAWT.lwText.LWTextComponent.setCaretPosition(Unknown Source)
      at oracle.forms.ui.delegates.VCommonTextDelegate.setProperty(Unknown Source)
      at oracle.forms.ui.delegates.VTextFieldDelegate.setProperty(Unknown Source)
      at oracle.forms.ui.VTextField.setProperty(Unknown Source)
      at oracle.forms.handler.TextComponentItem.onUpdate(Unknown Source)
      at oracle.forms.handler.TextFieldItem.onUpdate(Unknown Source)
      at oracle.forms.handler.UICommon.onUpdate(Unknown Source)
      at oracle.forms.engine.Runform.onUpdateHandler(Unknown Source)
      at oracle.forms.engine.Runform.processMessage(Unknown Source)
      at oracle.forms.engine.Runform.processSet(Unknown Source)
      at oracle.forms.engine.Runform.onMessageReal(Unknown Source)
      at oracle.forms.engine.Runform.onMessage(Unknown Source)
      at oracle.forms.engine.Runform.processEventEnd(Unknown Source)
      at oracle.ewt.lwAWT.LWComponent.redispatchEvent(Unknown Source)
      at oracle.ewt.lwAWT.LWComponent.processEvent(Unknown Source)
      at java.awt.Component.dispatchEventImpl(Unknown Source)
      at java.awt.Container.dispatchEventImpl(Unknown Source)
      at java.awt.Component.dispatchEvent(Unknown Source)
      at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
      at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
      at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
      at java.awt.Container.dispatchEventImpl(Unknown Source)
      at java.awt.Component.dispatchEvent(Unknown Source)
      at java.awt.EventQueue.dispatchEvent(Unknown Source)
      at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
      at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
      at java.awt.EventDispatchThread.run(Unknown Source)

Thanks for any help you can provide.

1 Solution
This looks like bug 338834.1 in Metalink

"If the following 2 conditions are met the forms is crashing:

1.display items have an initial value text with "carriage return" inserted into it
2.on the same form a button or a textitem is present and has the "Prompt" property set"


You can use a  work-around or upgrade to or apply a one off patch for : Patch 4658455:
donnelegAuthor Commented:
Thanks gatorvip, that sounded right except that we are upgraded to  The weird thing is I found an old reference to the actual problem, way back on Forms and Reports 6.  
The solution on 6 was to modify the field property 'Keep Cursor Position' from a Yes to a No.  My fields (in Forms and Reports 10) were already set to No.  Out of frustration, I set them to 'Yes' just to see what would happen.  Well, what happened is it fixed the problem.  I'm not sure if Oracle changed the behavior somewhere in there and just didn't document it.  Perhaps they fixed the problem from 6 and caused it on 10.  Either way, it works now.  
Sorry it took so long to get back to this board.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now