Field Validation Behaves Differently in dBASE IV & FoxPro

Last reviewed: June 28, 1995
Article ID: Q115954

The information in this article applies to:

Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6
Microsoft FoxPro for MS-DOS, versions 2.0, 2.5, 2.5a, 2.5b, 2.6
Microsoft FoxPro for Macintosh, versions 2.5b, 2.5c

SUMMARY

In dBASE IV, field validation will not occur unless a change is made in the field. However, in FoxPro, field validation is forced even though no change is made to the field. Issuing SET COMPATIBLE DB4 does not make FoxPro behave like dBASE IV.

MORE INFORMATION

To demonstrate this behavior, run the following code in FoxPro:

   SET COMPATIBLE DB4

   @ 10,10 GET memvar1 DEFAULT SPACE(10) VALID mytest()
   @ 11,10 GET memvar2 DEFAULT SPACE(10) VALID mytest()
   READ

   FUNCTION mytest
   WAIT WINDOW "In VALIDation function..."
   RETURN .T.

NOTE: Press ENTER in the GET fields.

Additional reference words: FoxMac FoxDos FoxWin 2.00 2.50a 2.50b 2.60
2.50c
KBCategory: kbprg
KBSubcategory: FxinteropDbase

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: June 28, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.