FIX: SQL PassThrough May Return Incorrect String (202621)
The information in this article applies to:
- Microsoft Visual Basic Enterprise Edition for Windows 4.0
- Microsoft Visual Basic Enterprise Edition for Windows 5.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP3
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP4
- Microsoft Visual Basic Enterprise Edition for Windows 6.0 SP5
- The DAO SDK 3.51
This article was previously published under Q202621 SYMPTOMS
When you use the DbSQLPassThrough constant in Data Access Objects (DAO) version 3.51, if the text is exactly 256 characters long, the last character is truncated and replaced with a "0" character. The same behavior also occurs if the text is exactly 511, 766, or 1,021 characters (and so on).
CAUSE
This error occurs because of UNICODE conversion problems that are located in the DAO/Jet SQLPassThrough engine.
RESOLUTION
You can use one of the following workarounds: - Upgrade to DAO 3.6/Jet 4.0.
- Use ODBCDirect to perform the query.
- Use Remote Data Objects (RDO) to perform the query.
- Use ActiveX Data Objects (ADO) to perform the query.
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
This bug was corrected in DAO 3.6/Jet 4.0. To use DAO 3.6 in your application, select the DAO 3.6 reference instead of the DAO 3.51 reference.
Modification Type: | Major | Last Reviewed: | 6/30/2004 |
---|
Keywords: | kbbug kbDatabase kbfix KB202621 |
---|
|