Remote OLE Links Between Documents Are Broken

Last reviewed: May 31, 1996
Article ID: Q149442
The information in this article applies to:
  • Microsoft Windows NT Workstation version 3.51
  • Microsoft Windows NT Server version 3.51

SYMPTOMS

If the component files used by an application are created on a shared network drive, the links established in the compound documents do not contain relative path specifications. An application based on the exchange of data between the various documents through OLE links will exhibit the following symptoms: If the users move the client files to their local drives, the links between the component files cannot be reestablished without unreasonable user intervention, and the application cannot function properly. The application will report various errors, such as "file not found."

CAUSE

When the component files are created on or saved to the network directory and then moved to identical relative positions on a different machine, the OLE links in compound documents are being broken. The same functionality works correctly if the files are originally created on the local drive.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 3.51. This problem was corrected in the latest U.S. Service Pack for Windows NT. For information on obtaining this update, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K


KBCategory: kbinterop kbfix3.51.sp4
KBSubcategory: nt32ap
Additional reference words: 3.51


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: May 31, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.