FIX: SET CPCOMPILE w/ Invalid Code Page Sets CPCOMPILE to 0

 Last reviewed: October 20, 1997
Article ID: Q119761
2.60 | 2.60 
WINDOWS   | MS-DOS
kbprg kbbuglist kbfixlist

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.6
  • Microsoft FoxPro for MS-DOS, version 2.6

SYMPTOMS

If you set CPCOMPILE to an invalid code page designation, CPCOMPILE will be set to 0, which is itself an invalid code page.

RESOLUTION

To avoid this problem, make sure that you are using a valid code page designation when you use the SET CPCOMPILE command.

STATUS

Microsoft has confirmed this to be a problem in FoxPro version 2.6 for Windows and MS-DOS. This problem was corrected in FoxPro version 2.6a for Windows and MS-DOS.

Additional reference words: FoxDos FoxWin 2.60 buglist2.60
FixList2.60a
zero
codepage
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxprgIntl
Keywords : FxprgIntl kbbuglist kbfixlist kbprg
Version : 2.60 | 2.60
Platform : MS-DOS WINDOWS
Solution Type : kbfix

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: October 20, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.