BUG: IOleObject::Close(OLECLOSE_NOSAVE) and DoVerb() (111577)
The information in this article applies to:
- Microsoft OLE Libraries for Windows and Win32s 2.01
- Microsoft OLE Libraries, when used with:
- the operating system: Microsoft Windows NT 3.5
- the operating system: Microsoft Windows NT 3.51
- the operating system: Microsoft Windows 95
This article was previously published under Q111577 SYMPTOMS
An OLE 2.0 container application inserts a new embedded object into a
document. The container calls IOleObject::Update() on the object to update
the cache, then calls IOleObject::Close(OLECLOSE_NOSAVE) to transition the
object back to the loaded state. Finally, the container tries to rerun the
object by calling IOleObject::DoVerb().
In this particular scenario, DoVerb() will return STG_E_FILENOTFOUND, and
the object will not be rerun.
CAUSE
Because the container specifies OLECLOSE_NOSAVE when calling Close(), the
object is never saved to persistent storage. However, the object has
internally been marked as not being a brand new object. Consequently, when
the container calls DoVerb(), the object's handler calls
IPersistStorage::Load() on the object, attempting to put the object into
the running state. This call will fail, because the object has never been
saved.
RESOLUTION
The solution to this problem is for the container to specify
OLECLOSE_SAVEIFDIRTY when calling Close().
STATUS
Microsoft has confirmed this to be a problem in the Microsoft products
listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 3/3/2005 |
|---|
| Keywords: | kbBug KB111577 |
|---|
|