BUG: Relative Monikers and OLE 1.0 Link Objects

• Microsoft OLE Libraries for Windows and Win32s, version 2.01

SYMPTOMS

When a link object from an OLE 2.0 application is copied to the clipboard and then pasted into an OLE 1.0 application, the OLE 2.0 emulation layer preserves the object's relative moniker. If the OLE 1.0 application document is closed and then reopened by an OLE 2.0 version of the application, OLE 2.0 will create a full moniker for the linked object by appending the preserved relative moniker to the file moniker for the document. This full moniker will be incorrect, because it will point to the new document rather than to the first OLE 2.0 application's document that contains the original linked object.

However, OLE 2.0 will still be able to bind to the linked object by following the absolute moniker that is also stored with the object (providing that the absolute location of the original linked object has not changed). At the time of this binding, OLE will then correct the full moniker for the object.

STATUS

Microsoft has confirmed this to be a problem with the Object Linking and Embedding libraries version 2.01. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.