ACC: MS Access Converts Extended Chars in Linked FoxPro DBF

 Last reviewed: May 28, 1997
Article ID: Q113303
The information in this article applies to:
  • Microsoft Access versions 1.1, 2.0, 7.0, 97
  • FoxPro for Windows versions 2.5a, 2.5b, 2.6

SYMPTOMS

Moderate: Requires basic macro, coding, and interoperability skills.

Extended characters (ANSI characters greater than 128) that you enter in an linked (attached) FoxPro table are converted to other characters when you commit the record.

CAUSE

The ISAM that Microsoft Access uses to link FoxPro databases reads a Code Page flag in the header of the FoxPro database. This flag tells the ISAM how to handle OEM to ANSI conversions. In this case, the flag is set to convert ANSI characters to OEM characters.

RESOLUTION

To prevent the ISAM from performing ANSI to OEM conversions, add the following line to the FoxPro configuration file CONFIG.FPW: 

   CODEPAGE=AUTO

MORE INFORMATION

The resolution above will not correct character conversions that were made prior to your changing the Config.fpw file. To correct conversions that have already been made, port the data from the existing FoxPro database to a new FoxPro database. Consult the FoxPro documentation for information on how to port data from an existing database to a new database.

Keywords : IsmXbase kb3rdparty
Version : 1.10 2.0 7.0 97
Platform : WINDOWS
Hardware : X86
Issue type : kbprb
Resolution Type : Info_Provided

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