This article applies to Microsoft Dynamics NAV for all countries and all language locales.
A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix. Note
In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements. Note
Before you install this hotfix, verify that all Microsoft Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. You should be the only client user who is logged on when you implement this hotfix.
To implement this hotfix, you must have a developer license.
We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
- The Modify permission for the object that you will be changing.
- The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.
You do not have to have rights to the data stores unless you have to perform data repair.
Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, change the code in the ShowMergedDocument
function in the WordManagement Codeunit (5054) as follows:
...IF ISCLEAR(wrdApp) THENCREATE(wrdApp,FALSE,TRUE);wrdDoc := wrdApp.Documents.Open(MainFileName,ParamFalse,Attachment."Read Only");wrdDoc.MailMerge.MainDocumentType := 0;...
...IF ISCLEAR(wrdApp) THENCREATE(wrdApp,FALSE,TRUE);wrdDoc := wrdApp.Documents.Open(MainFileName,ParamFalse,Attachment."Read Only" );// Add the following line.wrdApp.ActiveWindow.View.ReadingLayout := FALSE;// End of the added line.wrdDoc.MailMerge.MainDocumentType := 0;...
You must have one of the following products installed to apply this hotfix:
- Microsoft Dynamics NAV 2009 R2
- Microsoft Dynamics NAV 2009 Service Pack 1
You cannot remove this hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.