PRB: 32-bit BASIC Does Not Convert UNICODE/ANSI in Binary Field

• Microsoft Visual Basic Professional and Enterprise Editions for Windows, versions 5.0, 6.0
• Microsoft Visual Basic Professional and Enterprise Editions, 32-bit only, for Windows, version 4.0
• Microsoft Access versions 7.0, 97

SYMPTOMS

When using a binary field to store text in a Microsoft Jet 2.5 or earlier database, 32-bit applications cannot read text written by 16-bit applications and vice versa.

CAUSE

Unlike Memo fields, the 32-bit programs do no automatic ANSI/UNICODE conversion on binary fields.

RESOLUTION

1. Use the StrConv() function to perform explicit ANSI/UNICODE conversion.


-or-


2. Use MEMO fields instead of OLE/Binary fields for storing text. This is the preferred method.

STATUS

This behavior is by design.

MORE INFORMATION

Because the nature of data in a binary field is not predetermined, BASIC does no conversion when reading or writing data to these fields. This behavior creates a problem when 16-bit and 32-bit programs inter-operate, because 16-bit programs represent text as ANSI characters (1 byte per character) and 32-bit programs normally represent text as UNICODE characters (2 bytes per character).

32-bit programs can represent text as ANSI, but require explicit use of the StrConv() function to translate between UNICODE and ANSI, for example:

   strANSI = StrConv(strUNICODE, vbFromUnicode)

   strUNICODE = StrConv(strANSI, vbUnicode) 

Steps to Reproduce Behavior

1. Create a Jet 2.x database (DB1.MDB) using Access 2.0 or the VisData utility in Visual Basic 4.0 16-bit.



2. Create a table (Table1) with a numeric field (ID) and an OLE/Long Binary field (BLOB).



3. In Visual Basic 4.0 16-bit or Access 2.0, create a form with a CommandButton (Command1) and the following code:

   
         Private Sub Command1_Click()
         Dim db As Database, rs As Recordset
         Set db = DBEngine(0).OpenDatabase("DB1.MDB")  ' VB4
         Set db = CurrentDB()                          ' Access 2.0
         Set rs = db.OpenRecordset("Table1")
         rs.AddNew
         rs!id = 1
         rs!blob = "Test Message"
         rs.Update
         rs.Close
         db.Close
         End Sub 




4. Run the form and click the CommandButton to add a row to the database.



5. In Visual Basic 4.0 32-bit, Visual Basic 5.0, or Access 95 or later, create a form with two CommandButtons (Command1 and Command2) and the following code:

   
         Private Sub Command1_Click()
         Dim db As Database, rs As Recordset
         Set db = DBEngine(0).OpenDatabase("d:\win16app\vb4\db1.mdb")
         Set rs = db.OpenRecordset("Table1")
         Debug.Print rs!id, rs!blob
         Debug.Print rs!id, StrConv(rs!blob, vbUnicode)
         rs.Close
         db.Close
         End Sub
   
         Private Sub Command2_Click()
         Dim db As Database, rs As Recordset
         Set db = DBEngine(0).OpenDatabase("d:\win16app\vb4\db1.mdb")
         Set rs = db.OpenRecordset("Table1")
         rs.Edit
         rs!blob = StrConv("32-bit test message", vbFromUnicode)
         rs.Update
         rs.Close
         db.Close
         End Sub 

   NOTE: You must add a reference to Microsoft Data Access Objects 3.0 or 3.5 if running this code in Visual Basic 4.0 or 5.0 respectively.



6. Run the form and click Command1. The first line of output will contain the ID and a series of question marks illustrating that the ANSI to UNICODE conversion has not taken place. The second line of output, using the StrConv() function, correctly outputs the text.



7. Click Command2 to write converted data. You can click Command1 again to see that the data has been correctly converted from UNICODE to ANSI and back again.

REFERENCES

Microsoft Visual Basic Help Topic: StrConv()

© Microsoft Corporation 1998, All Rights Reserved.
Contributions by Malcolm Stewart, Microsoft Corporation

Additional query words: kbVBp500 kbVBp600 kbVBp kbdsd kbDSupport kbVBp400 kbNoKeyWord

Keywords : kbGrpVB kbGrpVBDB
Version :
Platform : WINDOWS
Issue type : kbprb