FIX: Accented Characters in Field Names Garbled

 Last reviewed: October 14, 1997
Article ID: Q107515
2.50a WINDOWS kbprg kbfixlist kbbuglist

The information in this article applies to:

  • Microsoft FoxPro for Windows, version 2.5a

SYMPTOMS

When CODEPAGE=AUTO, accented characters in field names are saved incorrectly when you modify the structure of a table that you've transported from another platform.

STATUS

Microsoft has confirmed this to be a problem in FoxPro 2.5a for Windows. This problem was corrected in FoxPro 2.5b for Windows.

MORE INFORMATION

Steps to Reproduce Problem

  1. Create a table in FoxPro 2.5a for MS-DOS with one field called "x". Make sure that CODEPAGE=AUTO is in the CONFIG.FP file.

  2. Quit FoxPro for MS-DOS.

  3. Start FoxPro 2.5a for Windows. Make sure that CODEPAGE=AUTO is in the CONFIG.FPW file.

  4. In the Command window, type the following: 

          USE <database>

  5. From the Database menu, choose Database Structure.

  6. Change the field called "x" to "a" with an umlaut (ALT+132). Save the changes to make them permanent.

  7. Browse the database. The field appears with the new name.

  8. Close and reopen the database.

  9. Browse the database. The field name contains garbled characters.

Additional reference words: FoxWin 2.50a buglist2.50a fixlist2.50b MODIFY
STRUCTURE diaeresis dieresis diacritical marks acute grave circumflex
extended character set
KBCategory: kbprg kbfixlist kbbuglist
KBSubcategory: FxenvConfigfp
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 14, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.