Note: This information applies only to a Microsoft Access databases.
Starting with Microsoft Access 2000 and continuing through the current version, all data for the Text data types (Text, Memo, or Hyperlink field) are stored in the Unicode 2-byte character format. Languages such as Chinese, Japanese, and Korean use the full 2-byte characters, but languages that use Latin characters (e.g. English, Spanish, and German) always use a 0 as the first byte. When a field's Unicode Compression property is set to Yes, any character whose first byte is 0 is compressed when it is stored and uncompressed when it is retrieved, thus saving space in the database.
By default, Unicode Compression is set to ‘Yes’ when you create the field via the table properties. It is when you create the field via SQL that you must explicitly state the Unicode Compression to be ‘Yes’. Otherwise, the setting is left untouched with a value of ‘No’. To see the property to ‘Yes’, use the WITH COMPRESSION (or WITH COMP) keywords at the field-level declaration.
The Unicode Compression is a property setting of the field. After making the data type selection, the property is located on the General tab at the bottom of the table property page.
FMS's Total Access Analyzer performs detailed analysis of your Access database objects. The detection of the Unicode Compression property is just one of hundreds of checks that can be performed on your Microsoft Access application.
The following example illustrates two fields, with and without Unicode Compression being set.
Public Sub CompressionPropertyTest() Dim strSQL As String strSQL = "Create Table MyFirstTable ( FirstName_CompressionOFF Text(15), " & _ "LastName_CompressionON Text(15) WITH COMPRESSION)" CurrentProject.Connection.Execute strSQL End Sub
Thank you! Thank you! I just finished reading this document, which was part of a link in the recent Buzz newsletter. I have printed it for others to read, especially those skeptical on the powers of Access and its capabilities.