BUG: Program Crashes When Memo Field Mapped to CLongBinary

Last reviewed: July 2, 1997
Article ID: Q130438
1.52    | 2.10
WINDOWS | WINDOWS NT kbprg kbbuglist

The information in this article applies to:

  • The Microsoft Foundation Classes (MFC) included with:

        - Microsoft Visual C++ for Windows, version 1.52
        - Microsoft Visual C++, 32-bit Edition, version 2.1
    

SYMPTOMS

Using the RFX_LongBinary() record field exchange (RFX) function to map a Microsoft Access version 2.0 memo field to a CLongBinary object causes a general protection (GP) fault with a 16-bit application or an access violation with a 32-bit application.

The error occurs when trying to read the data, specifically when calling SQLGetData().

CAUSE

This is caused by a bug in the ODBC version 2.1 Microsoft Access version 2.0 driver included with Visual C++ versions 1.52 and 2.1.

RESOLUTION

Do one of the following:

  • Use the RFX_Text() function to map the memo field to a CString instead of using CLongBinary.

    -or-

  • Change the Memo field into an OLE Object field (a binary field), and continue to use CLongBinary.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional reference words: 2.10 GPF noupdate
KBCategory: kbprg kbbuglist
KBSubcategory: MFCDatabase
Keywords : MFCDatabase kbbuglist kbprg
Technology : kbMfc
Version : 1.52 | 2.10
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: July 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.