Article List for Problems With a CLongBinary Field

 Last reviewed: October 10, 1997
Article ID: Q118758
1.50 1.51 1.52 | 2.00 2.10 2.20 4.00 4.10 
WINDOWS        | WINDOWS NT
kbprg kbbuglist kbfixlist

The information in this article applies to: 

   The Microsoft Foundation Classes (MFC) included with:
   - Microsoft Visual C++ for Windows, versions 1.5, 1.51, and 1.52
   - Microsoft Visual C++ 32-bit Edition, versions 2.0, 2.1, 2.2, 4.0
     and 4.1

SUMMARY

The following articles describe issues associated with using a CLongBinary Field. 

ITEM ID   ARTICLE TITLE
-------- ---------------------------------------------------------- 

Q126264  CLongBinary Field Truncated with SQL Server ODBC Driver
Q130438  BUG: Program Crashes When Memo Field Mapped to CLongBinary
Q132399  PRB: SQLGetData() Returns SQL_NO_TOTAL in RFX_LongBinary()
Q141352  FIX: Only 64K of Data Transferred via CLongBinary
Q140533  FIX: "SQLPutData Length exceeded" For Data Exceeding 64K

Q140534  BUG: "Data Truncated Column" Erroneously Reported
Q140535  FIX: Only First 64K is Read From Binary Field
Q150408  BUG: Data Entered w/HGLOBAL Not Placed in Table
Q141303  FIX: Dynasets w/ CLongBinary Fields Throws Incorrect Exception
Q147948  BUG: Errors Occur Using DAO CLongBinary Data from Database

Q149137  BUG: ODBC Long Binary Functions Use SQL_NO_TOTAL Incorrectly
Q149139  FIX: Visual C++ Breaks ODBC CLongBinary w/ GlobalReAll Misuse
Q153888  PRB: RFX_LongBinary not Optimized for SQL Server

Additional reference words: kbinf 2.50 2.51 2.52 4.00 4.10 kblist
KBCategory: kbref
KBSubcategory: RefsPSS
Keywords : RefsPSS kbref
Technology : kbMfc
Version : 1.50 1.51 1.52 | 2.00 2.10 2.20
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.