BUG: Blob Persistent Data Incorrect for Ported OLE Control (142211)
The information in this article applies to:
- The Microsoft Foundation Classes (MFC), when used with:
- Microsoft Visual C++, 32-bit Professional Edition 4.0
- Microsoft Visual C++, 32-bit Professional Edition 4.1
- Microsoft Visual C++, 32-bit Learning Edition 4.0
This article was previously published under Q142211 SYMPTOMS
An OLE control using PX_Blob(), created using the Control Developer's Kit
(CDK) that shipped with Visual C++ 2.2 or earlier and saved in a Visual
Basic 4.0 form, may give undefined behavior if the control is ported to
Visual C++ 4.0 or 4.1 and the Visual Basic form containing the control is
reopened.
To read in the blob data correctly, you must force the container to use an
interface other than IPropertyBag to serialize the data. In this case, a
20-byte header will not be expected and the blob data should be read in
properly. The technique demonstrated in the "Sample Code" section of this
article unexposes the control's IPersistPropertyBag interface thereby
forcing the container to use an interface other than IPropertyBag to read
in the blob data.
CAUSE
OLE Controls created using the CDK that shipped with Visual C++ 2.2 or
earlier did not implement the IPersistPropertyBag interface. Controls
created with Visual C++ 4.0 or 4.1 do implement IPersistPropertyBag.
The undefined behavior is due to Visual Basic's implementation of
IPropertyBag. Visual Basic is currently adding a 20-byte header to a blob
property's persistent data, and expecting that header to be in any blob
persistent data previously saved. In the case of controls created
previously to Visual C++ 4.0 or 4.1, IPersistPropertyBag, which corresponds
to the container's IPropertyBag was not implemented. Therefore, the
container used a different means to serialize the blob data which did not
attach a 20 byte header. The undefined behavior may behave a number of ways
including the blob data being reinitialized, blob data being initialized
incorrectly, or the control not being created altogether.
STATUS
Microsoft has confirmed this to be a bug in Microsoft Visual Basic 4.0.
REFERENCES
MFC Technical Note #38 about "MFC/OLE IUnknown implementation"
Inside Ole Second Edition by Kraig Brockschmidt
Modification Type: | Major | Last Reviewed: | 12/8/2003 |
---|
Keywords: | kbBug kbCtrl kbVBX KB142211 |
---|
|