BUG: OLE 2.0 Containers & 1.0 Objects that Close w/out Saving

View products that this article applies to.

This article was previously published under Q109547

Expand all | Collapse all

SYMPTOMS

When an OLE 1.0 object is inserted into an OLE 2.0 container document and then closed without an update being invoked, the correct streams for that object are not written to storage. Any subsequent attempt by the container to load the object will fail.

Back to the top

CAUSE

When the OLE 1.0 object is closed without an update, the OLE 2.0 container receives an IAdviseSink::OnClose() message without having first received an IClientSite::SaveObject() message. Unless the container takes steps to work around this problem, incorrect streams will be saved.

Back to the top

RESOLUTION

To protect against this scenario, OLE 2.0 containers that want data to be available after an OLE 1.0 object closes without updating can implement code similar to the following pseudocode:

   OleCreate();
   OleRun();
   IOleObject::Update();       \\ To get a snapshot of the data.
   OleSave();                  \\ To save the data to storage.
   IOleObject::DoVerb();

Alternatively, the container could just delete any objects that call IAdviseSink::OnClose() without first calling IClientSite::SaveObject().

Back to the top

STATUS

Microsoft has confirmed this to be a problem in the products listed at the beginning of this article. We are researching this problem and will post new information here as it becomes available.

Back to the top

MORE INFORMATION

For more information about known idiosyncrasies of embedding or linking OLE 1.0 objects into OLE 2.0 containers, please see the "Compatibility with OLE 1.0" section of the OLE SDK Help file.

Back to the top