BUG: After Editing Memo Field Cursor Moves to 1st GET Object

• Microsoft FoxPro for Windows, versions 2.5x, 2.6, 2.6a
• Microsoft FoxPro for MS-DOS, versions 2.0, 2.5x, 2.6, 2.6a

SYMPTOMS

After the user edits a memo field, the cursor automatically returns to the first GET object on the current screen when the user edits the memo field in a GET field or in a separate window. When the memo field is edited in an edit region, the cursor remains in the memo field after editing is complete.

RESOLUTION

To return the cursor to the memo field after editing is complete, do one of the following:

• In the Screen Builder, specify the field as an EDIT field instead of a GET field.

  -or-

• Add a valid clause to the GET statement for the memo field, as follows:

        GET memofield VALID movecur()
        READ
  

        PROCEDURE movecur
        _curobj=_curobj
  

  To place the cursor on the field following the memo field, change the "_curobj=_curobj" statement in the movecur procedure to read as follows:

        _curobj=_curobj+1
  

  -or-

• Open the Windows Control Panel, choose the Fonts icon and install FOXFONT.FON. You must distribute FoxFont with your .EXE files so that the Browse windows, list boxes, and other objects will maintain their correct positions.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.