Did you ever had an issue where Navision where freezing when opening a Document from then Interaction Log.
Actually Navision could also be freezing when creating a Interaction Log Entry that uses Word.
So why is Navision freezing?
Well if you start a debugger you might notice that it is codeunit 5054, function WordHandler that is causing it.
Navision is freezing while waiting for Word to close.
The call wrdHandler.WaitForDocument(wrdDoc) does never receive a notice from Word, when it is being closed and thereby Navision is freezing.
So why does the wrdHandler never get an answer?
Well it is often caused by the Microsoft Office installation. If you open Word separately you might get an warning about macro support not being installed and here we have the reason.
If you go into the Microsoft Office Installation and look into Office Shared Features, you will noticed the Visual Basic for Applications is not installed.
When Visual Basic for Applications is not installed, then Word is not returning any information to other Applications that are executing it.
So if you install Visual Basic for Applications, then Navision should not freeze anymore 🙂
Pretty simple solution – if you know what is causing Navision to freeze 😉
Wonderful, what a weblog it is! This blog provides helpful data to us, keep it up.