BUG: OLE 2.0 Compatibility Layer Uses Document IDataObjectLast reviewed: May 17, 1995Article ID: Q111585 |
The information in this article applies to:
SYMPTOMSWhenever the OLE 1.0 client compatibility layer uses IDataObject, it uses the OLE 2.0 server's document-level data object rather than the server's pseudo-object data object.
STATUSMicrosoft has confirmed this to be a problem 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.
MORE INFORMATIONOne of the side-effects of this problem is that the following key is required in the OLE 2.0 server application's CLSID listing in the registration database
GetSet |- X = 3, 1, 32, 1where X is application-dependent. If this key is missing from the registration database, then any attempt to embed the OLE 2.0 object into an OLE 1.0 client will fail, even if the server application fully supports IDataObject::EnumFormatEtc. The GetSet key is used by server applications to describe the formats that an object is capable of rendering, or having set. OLE looks at this key when it needs to know which formats an object supports, without having to run the object. This key is required in this situation because the OLE 1.0 compatibility layer is always going to refer to the registration database to enumerate the formats supported by the server application. This particular key represents the METAFILEPICT format, which must be supported for OLE 1.0 compatibility.
|
Additional reference words: 2.01 3.50 4.00 toolkit
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |