BUG: OLE 2.0 Compatibility Layer Uses Document IDataObject

MORE INFORMATION

One 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, 1
				

where 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.