I have just converted a FoxPro 2.6 system to 6.0, retaining almost all the
procedural code and just tweaking it to handle the differences. I've dealt with
Valid clauses, unsaved changes in GET fields, strange behariors related to ACTI
Screen, but I've run into a problem best described in the following psuedo-code.

PROC DocNotes
USE Doc IN 0
USE Hos IN 0

ON KEY LABEL F5 DO HosNotes
DEFINE WINDOW DocNote FROM 2,3 TO 12,60 ....
MODI MEMO Doc.Notes WINDOW DocNote
RETU

PROCEDURE HosNotes
ON KEY LABEL F5
DEFINE WINDOW HosNote FROM 6,8 TO 14,65....
MODI MEMO Hos.Notes WINDOW HosNote
ON KEY LABEL F5 DO HosNotes
RETU

In 2.6, DOing DOCNOTES would let the user modify the Doc notes, press F5 and modify the Hos notes in a separate window. When the user Escaped or Ctrl+W'd out of hos notes, the DocNotes memo window would reactivate. Pretty much your basic modeless behavior.

In 6.0, the HosNotes procedure executes, but when the MODI MEMO Hos.Notes line executes,the hos notes flash on screen for less than a second, and execution proceeds to the line after MODI MEMO hos.Notes.

Has anyone encountered this and found a workaround? I suppose I could resort to using a form with a textbox in the place of MODI MEMO, but if there is some simple change I can make to the existing code, Id' rather take that approach.