BUG: Data Entered with HGLOBAL Is Not Placed in TableLast reviewed: July 2, 1997Article ID: Q150408 |
1.50 1.51 1.52
WINDOWS
kbprg kbbuglist
The information in this article applies to:
SYMPTOMSData entered in the memory associated with the HGLOBAL of the CLongBinary is not placed in the table.
CAUSEWhen data is placed in a binary large field with CLongBinary, the dirty flag for the field needs to be set for an Update() call. For more information, see MFC TechNote #45. Also, if the CRecordset is on a record in which the binary field is currently NULL and you are changing the data, you need to clear the NULL flag and the dirty flag for that field before calling Update().
RESOLUTIONSet the dirty flag by calling SetFieldDirty(), and clear the NULL flag by calling SetFieldNull() with a argument of FALSE.
STATUSMicrosoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
|
Additional reference words: 1.50 1.51 1.52
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |