The information in this article applies to:
SYMPTOMSWhen using a Snapshot recordset with the CRecordset class, if you delete the contents of a CString mapped to a memo field in a Microsoft Access database, nothing is actually deleted in the database. In other words, the data that previously existed in the field remains in that field. However, the recordset still shows that the field has been changed to null but it has only been changed in the cache of the cursor library, not the database. CAUSEA problem exists in the ODBC cursor library which is used by default in MFC. RESOLUTION
This problem was resolved with the ODBC Cursor Library that ships with
Visual C++ 4.0 for 32-bit ODBC components and remains unresolved for 16-bit
ODBC components.
Q124915 SAMPLE: Using Dynasets with the 16-Bit MFC Database Classes If you cannot use dynasets, then you need to replace "empty" memo fields with a single space. The code below shows how to use this solution with a CRecordView derived class. STATUSMicrosoft 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. MORE INFORMATIONSample CodeThe code below is from a CRecordView derived class using a recordset for an Access data source, which has a memo field that maps to m_Memo.
Additional query words: kbmfc kbdatabase kbodbc kbvc150bug kbvc151bug kbvc152bug
Keywords : |
Last Reviewed: September 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |