The information in this article applies to:
SYMPTOMSVisual FoxPro for Windows 3.0x and 5.0 invoke the VALID clause upon execution of a MODIFY MEMO command, whereas FoxPro for Windows 2.6x does not. WORKAROUNDThe suggested workaround is to set a flag based on the version and test the flag prior to executing any Valid code. STATUSThis behavior is by design. MORE INFORMATIONSince Visual FoxPro for Windows is now object-oriented, the Valid event is firing properly. The cursor has indeed left the GET field; therefore, the MODIFY MEMO window now has the focus. Steps to Reproduce BehaviorEnter and run the following program in both Visual FoxPro 5.0 (or 3.0x) and FoxPro for Windows 2.6x and notice that Visual FoxPro invokes the READ VALID clause, whereas FoxPro for Windows does not. On the Program menu, click Cancel to exit the program:
© Microsoft Corporation 1997, All Rights Reserved. Additional query words:
Keywords : kbinterop kbVFp kbVFp300 kbVFp500 kbVFp600 FxinteropPrevfox FxprgRead |
Last Reviewed: December 13, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |