OLE Object Names Must Be Unique

Last reviewed: February 17, 1995
Article ID: Q71659

The information in this article applies to:

Microsoft OLE version 1.0

Names given to embedded or linked objects in client documents must be unique. The application must preserve these names across the saving and closing of the client document.

To open the client document, the client application calls OleLoadFromStream. One of the parameters to this function is the object name. For a given object, this name must be the same as when the object was saved to disk. Essentially, this means the object name must be saved along with other pertinent data. It is the client application's responsibility to assign a unique object name when the object is created and to preserve the uniqueness.

Currently, an application may function properly if object name uniqueness is not maintained. However, it is very likely that future versions of the OLE libraries will cause applications using nonunique names to fail.

Additional reference words: 1.00 object linking embedding OL&E
KBCategory: kbole kbprg
KBSubcategory: LeoneCliName

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 17, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.