Knowledge Base |

# ACC: Microsoft Access Converts Extended Characters in Linked FoxPro DBF

Article ID: 113303

Article Last Modified on 1/18/2007

APPLIES TO

- Microsoft Access 1.1 Standard Edition
- Microsoft Access 2.0 Standard Edition
- Microsoft Access 95 Standard Edition
- Microsoft Access 97 Standard Edition
- Microsoft FoxPro 2.5a
- Microsoft FoxPro 2.5b
- Microsoft FoxPro 2.6 Standard Edition

This article was previously published under Q113303
Moderate: Requires basic macro, coding, and interoperability skills.

## SYMPTOMS

Extended characters (ANSI characters greater than 128) that you enter in a 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

This resolution 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: kb3rdparty kbprb KB113303