Question: There is garbled when writing Chinese in the Access database in the Access database in the VC, and garblered in the form of "Ingry is reilant" or "hafnium hafnium hafnium".
Workaround: When the field definition of the Access database, the value of "text" format field, "Unicode compression" is changed from "Yes".
Source: Office Help Document.
About compressed "Text", "Note" or "Hyperlink" field (MDB) Note This topic is only available for Microsoft Access database (.mdb).
Microsoft Access 2000 or later uses Unicode (Unicode: Unicode Consortium developed a character encoding standard. This standard uses multiple (one) bytes represent each character, realizing almost all written written in the world using a single character set. Language.) Character encoding scheme to represent "Text" data type: a field data type in the Microsoft Access database. "Text" data type can contain up to 255 characters, or a small smaller specified by the fieldsize property Some characters.), "Remarks" data type: a field data type in the Microsoft Access database. The "Remarks" field can contain 65,535 characters.) Or "hyperlink" ("hyperlink" "Data Type: Store the data type of the Access database field of the hyperlink address. The address can contain up to four parts, write data in the DISPLAYTEXT # Address # Subaddress #.) Field in the following speech. Unicode represents each character as two bytes, so "Text", "Note", or "Hyperlink" field, the required storage space is much more than in Access 97 or earlier, in Access 97 or Earlier versions are represented as a byte.
It can make up the impact of Unicode character expressions by setting the default value of "text", "note" or "hyperlink" field to "Yes" to ensure optimized performance. When the "Unicode Compressed" property of the field is set to "Yes", the characters of any first byte are compressed when the store is stored, and is decompressed at the time of extraction. Because the first byte of Latin characters (Western Europe language such as English, Spanish or German) is 0, the expression of Unicode characters does not affect the storage space required to compress data consisting entirely of Latin characters.
Any character combination supported by Unicode can be stored in a single field. However, if the first byte of a character is not 0, the character is not compressed.
The data in this field is not compressed unless the "Note" field needs 4,096 bytes or less space, otherwise the data in this field is not compressed. Therefore, the contents of the Note field may be compressed in a record, but not compressed in another record.
