A request is sending a message through msmq to Navision, and then receiving a response from Navision.

At first we though that this was cause by using bad keys, so we used client monitor to analyze the Poller – but no, this was not the case.

Another cause could be that the production environment has more users and thereby also more load – but again, the production server was not loaded so much that a request should take so much more time.

Then by lucky coincidence we tried to change the net type of the client – and now we saw a difference. Suddenly a request on the production environment only took approx. 3/400 ms – which is in the accepted time range.

So in this case it was better to use Netbeui than TCP even though Navision does not recommend the use of Netbeui.

So why is Netbeui faster than TCP? A reason could be that Netbeui uses smaller packets than TCP, and they will therefor travel faster since they have less overhead and have less to read.

I would though not recommend always to use Netbeui, because a Netbeui packet does not include logical destination address, only a name. The Netbeui protocol cannot be routed – this means that communication between hosts is limited to occurring within a single non-routed network, and is thereby not well suited for large networks.

But again – in this case Netbeui was a better choice.

The syntax for starting a Navision Client is:

navision://client/run

A call like this, in a browser, would start or activate a Navision Client. This call thou would prompt the user for login, password etc. So to simplify the user interaction, it is also possible to pass on some parameters.

Possible parameters are:

company	The company that should be open when starting the Navision Client
database	Database Name
servername	Server Name for the server you wants to connect to
servertype	Is it a native or mssql server?
target	Which object has to be activated. Ex. a Form18 – the syntax is [objecttype][objectno]
view	View (Filters) for the object, that will be activated with the target property

A complete url call could look like this:

navision://client/run?servername=myserver&
………………………database=mydb&
………………………company=mycompany&
………………………servertype=mssql&
………………………target=Form18&
………………………view=SORTING(No.) WHERE (No.=FILTER(132))

Remember when using a Navision protocol, it would be an advantage using windows authentification (windows login) for Navision – else your users would be prompted for username/password. Alternative you have to make sure, that a client already is running, before using the protocol.