Microsoft KB Archive/134741

= Embedded Office Object/Lotus Notes Form Fields Not Exchanged =

Article ID: 134741

Article Last Modified on 8/16/2005

-

APPLIES TO


 * Microsoft Office 4.2c
 * Microsoft Office 4.3c
 * Microsoft Office 95 Standard Edition
 * Microsoft Excel 5.0c
 * Microsoft Excel 95 Standard Edition
 * Microsoft PowerPoint 4.0c
 * Microsoft Word 6.0c

-



This article was previously published under Q134741





SYMPTOMS
When you insert an object created by one of the Microsoft Office applications listed above in a Lotus Notes form, the object fields are not updated with the Lotus Notes field information, and vice versa.



CAUSE
This problem occurs if you are running Lotus Notes from a Banyan Vines network server, and the Office application that you used to create the object that you inserted in the form (server application) is running. For example, if you are running Lotus Notes on a Banyan Vines server, when you insert a Microsoft Word document object in a Lotus Notes form while Microsoft Word is running, the document object fields are not exchanged with the fields in the form.

This behavior occurs because when you run Lotus Notes from a server instead of from a Workstation installation, the .dll files necessary for using Lotus Notes Field Exchange are not in the path on your computer. Office looks for the following .dll files to exchange data with Lotus Notes: _Sdk.dll, _Nsf.dll, and _Lib.dll.



RESOLUTION
To work around this problem when you are running Lotus Notes from a Banyan Vines server, use any of the following methods:

Method 1: Close the Microsoft Office application that you used to insert the object in the Notes form.

Method 2: Copy the necessary .dll files (_Sdk.dll, _Nsf.dll, and _Lib.dll) from the Lotus Notes installation on the Banyan Vines server to a directory in your path statement, such as the System directory in your Microsoft Windows directory.



STATUS
Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

