TechBlog

A guy I know wanted to reuse objects from NAV 2009 in a NAV 5.0 SP1 but had some difficulties by doing it.

In the Navision versions below 2009 you could easily reuse objects. For example there were no problems in moving objects between NAV 4 and NAV 5. So why are there problems when moving objects from NAV 2009 to NAV 5.0 SP1?

Most users will think there is no problem, due to the fact that NAV 2009 is basically just a NAV 5.0 SP2 – but they will get wiser. Read the rest of this entry »

If you are using the Role Tailored Client and want to use the Forms in it, you have to transform them to Pages. In NAV 2009 you can transform Forms to Pages with the help of the form transformation tool.

So the first thing to do – is to install the form transformation tool. To install the form transformation tool, just copy the contents of the transformation tool folder to any location on the Microsoft Dynamics NAV 2009 server. Read the rest of this entry »

XMLports was introduced with Navision 4.0 – they act like dataports, with a small difference. They can only be used for XML-formatted data and they must by executed from some other routine.

In the XMLport designer – you set up a defined format. Just think of it, as a kind of schema (xsd). You can add Elements and Attributes and in the Properties you can setup the Encoding and the DefaultNamespace. Read the rest of this entry »

Hi!

Lately I have been talking with some people, which have received the error “Could Not Load Type Library”. All these errors were caused by missing registration of the NSAppHandler.dll.

The NSAppHandler.dll can be registered in the following steps: Read the rest of this entry »

Hi!
Last week I did attend the Mibuso Conference in Mechelen, Belgium.

This was a very interesting Conference! On the Agenda was:
• Next Generation Unified Communications Platform
• Dynamics NAV
• Delivering Software to a Global Audience.

Read the rest of this entry »

If you have installed Visual Studio you will notice the Windows Runtime Debugger has been replaced with the “Just-In-Time Debugger”. Sometimes this is Ok, but if you are running jobs that need to be running silence, then this is not always a good thing.

So what to do? Just change the Windows Runtime Debugger back to Dr Watson. You can do this by using the command drwtsn32 -i. Just run it in a command prompt and the Windows Runtime Debugger is back to Dr. Watson.