XCLN: Posted Word for Windows Document Filename Changes

Last reviewed: March 31, 1997
Article ID: Q147282
The information in this article applies to:
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows NT client, versions 4.0 and 5.0

SYMPTOMS

In the Microsoft Exchange client version 4.0 for Windows, you can post documents to Exchange folders. These documents can then be edited with the application that created it.

When you edit a posted Microsoft Word for Windows document, the filename changes to "Document in Microsoft Exchange." The filename in the title bar also changes to "Document in Microsoft Exchange."

STATUS

Microsoft has confirmed this to be a problem in the Microsoft Exchange version 4.0 Windows client. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

This becomes a problem when the FileName field is used in the document. When the FileName field is inserted into a Word document, it shows the filename for that document.

For example, if you have a Word document called TEST.DOC, the results of the FileName field would be "TEST.DOC." When this document is posted to an Exchange folder, the result would change to "Document in Microsoft Exchange."

Other document types are not affected (for example, Microsoft Excel, Microsoft PowerPoint, Notepad, and so forth).


Additional query words: interop embed message
Keywords : kbbug4.00 kbinterop XCLN
Version : 4.0 5.0
Platform : WINDOWS


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