ACC2000: Thai Characters Are Not Displayed Correctly in Data Imported from Thai Database (288112)


The information in this article applies to:

  • Microsoft Access 2000
This article was previously published under Q288112
For a Microsoft Access 2002 version of this article, see 275109.
Novice: Requires knowledge of the user interface on single-user computers.

This article applies only to a Microsoft Access database (.mdb).

SYMPTOMS

When you view data that you imported from a Microsoft Access Thai database, which was created in a version of Access earlier than Access 2000, the Thai characters may not be displayed correctly, even though the Thai language setting is selected.

CAUSE

This behavior can occur because there is an issue with converting the characters from American National Standards Institute (ANSI) to Unicode. Versions of Access earlier than Access 2000 are not Unicode-based, and therefore the characters cannot be imported successfully into versions of Access later than Access 97.

RESOLUTION

To successfully import and display the Thai characters in Access 2002, make sure that the new file location is on a computer with a Thai language-based operating system.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

MORE INFORMATION

Steps to Reproduce the Problem

  1. Start Access and open a new blank database.
  2. On the File menu, point to Get External Data, and then click Import.
  3. Navigate to the folder that contains a Thai database created in a version of Access earlier than Access 2000, select it, and then click Import.
  4. In the Import Objects dialog box, click Select All, and then click OK.
  5. In the Database window, click Tables under Objects, and then click one of the tables that you imported from the Thai database. Notice that Thai characters are not displayed correctly, and that the Baht sign may disappear when you select a data field in which it resides.
Modification Type:MajorLast Reviewed:6/25/2004
Keywords:kbbug kbnofix KB288112
©2004 Microsoft Corporation. All rights reserved.