Using NAV Developer’s Toolkit with Microsoft Dynamics NAV 2009 SP1

I’ve been  encountering SQL Trace Flag 4616 issues when attempting to open a NAV 2009 R2 SQL database with the latest NDT Microsoft Dynamics NAV Developer’s Toolkit. I was a little taken aback  being aware that from NAV 5 Sp1 latest build, Trace Flag 4616 is no longer required. However, little did I know that Microsoft have somehow failed to update the underlying  compatibility support files which will enable the Tool to automatically comply with NAV 2009 SP1 to R2 Databases (SQL).  Anyway,  long story short, the following error Error messages were sequentially triggered when attempting to open NAV SQL database:

NDT Trace Flag Error

Trace Flag Error

 

Microsoft has provided a walk-around for this issue

The latest version of the Microsoft Dynamics NAV Developer’s Toolkit (version 3.01.410) is developed for Microsoft Dynamics NAV 2009. Therefore, you need to create the Developer’s Toolkit database with Microsoft Dynamics NAV 2009 client executables.

This How To article describes how you can make version 3.01.410 of the Developer’s Toolkit work with a Developer’s Toolkit database created with Microsoft Dynamics NAV 2009 SP1 client executables.

The Microsoft Dynamics NAV Developer’s Toolkit (NDT) uses C/Front to connect to the NDT database.  You can make the Developer’s Toolkit connect to a database that was created with Microsoft Dynamics NAV 2009 SP1 client executables by following these steps:

Install a Microsoft Dynamics NAV 2009 SP1 Classic client

Install the Microsoft Dynamics NAV Developer’s Toolkit version 3.01.410

Create the Developer’s Toolkit database following the instructions in the Developer’s Toolkit manual

Install C/Front for Microsoft Dynamics NAV 2009 SP1

Copy the following C/FRONT files from the C/Front installation folder to the Developer’s Toolkit folder:

  1. CFRONT.DLL
  2. cfront.ocx
  3. cfrontsql.dll
  4. Microsoft.Dynamics.NAV.CFront.CFrontDotNet.dll
  5. Microsoft.Dynamics.NAV.CFront.CFrontDotNet.xml

Note:

C/Front is by default installed in the following directory: C:\Program Files\Microsoft Dynamics NAV\60\SDK\CFRONT.

The Developer’s Toolkit is by default installed in the following directory: C:\Program Files \Microsoft Dynamics NAV\Developers Toolkit

Copy the following files from the Microsoft Dynamics NAV Classic client folder to the Developer’s Toolkit folder:

  1. nc_netb.dll
  2. nc_tcp.dll
  3. nc_tcps.dll
  4. ndbcs.dll
  5. slave.exe
  6. dbm.dlll

Note:

The Microsoft Dynamics NAV Classic client is by default installed in the following directory: C:\Program Files\Microsoft Dynamics NAV\60\Classic

The Developer’s Toolkit is by default installed in the following directory: C:\Program Files \Microsoft Dynamics NAV\Developers Toolkit

You can find the Microsoft Dynamics NAV 2009 SP1 Classic client and C/Front for Microsoft Dynamics NAV 2009 SP1 on the Microsoft Dynamics NAV 2009 SP1 installation media, which can be downloaded here: Microsoft Dynamics NAV 2009 Service Pack 1 (SP1).

You can download the Microsoft Dynamics NAV Developer’s Toolkit here: Developer’s Toolkit for Microsoft Dynamics NAV. Please note that access to Microsoft Partnersource is required in order to download this Tool.

via How to Use the Microsoft Dynamics NAV Developer’s Toolkit with Microsoft Dynamics NAV 2009 SP1.

Microsoft Dynamics NAV 2009 Upgrades and the RTC Reporting Nightmare – Erik P. Ernst about Navision and the Dynamics Community – Dynamics User Group

Typically I’m not the one who is writing too much about “technical issues” in my blog. But that doesn’t mean that I’m never dealing with “technical issues” – in fact programming and other technical issues is what I’m doing more than 50% of daily working time. And while this blog post is more “technical” than normally, then it’s not really technical. It’s more about my experiences with NAV 2009 upgrades as seen on a little higher level.

Until recently then I have not been doing so much work on NAV 2009. Most of my client as a freelancer have older versions, and are very happy about it. But now I have just finished my first full Dynamics NAV 2009 upgrade. Before I have done one other NAV 2009, but to a client who didn’t want to use the RoleTailored Client. And right now I’m doing my second RTC upgrade. Not much for many of you, but surely enough to get the feeling of what this “NAV 2009” is all about!

On the surface, then a NAV 2009 upgrade isn’t that much different from any other Navision upgrade. And over the 20 years where I have been working with Navision then I surely have done my share of the upgrades. And until NAV 2009, then it has always been almost like riding a bicycle. Once you have learned, then you will always have it.

Upgrading Pages

For Dynamics NAV 2009 then it was going great with the tables, forms, codeunits etc. All the object types that didn’t change too much from the previous versions. And when it came to the forms, then in both of the projects, I actually decided to create the new pages again using the page designer, instead of actually using the Page Transformation Tools. I did this basically because I’m a bit lazy of nature, and I estimated that it would take me much more time to setup and define the files for the Page Transformation Tool, than to manually upgrade the changed forms and to recreate the 10 new forms that the customer had in his database.

So I can’t even say how much it takes to use the Transformation Tools. At least there is a lot of documentation available regarding page transformation, so I am actually felt quite comfortable that it would not had been a problem, in case the client would have had a lot of new forms. But it is my own estimate that it would require at least 30-50 new forms, before it would be worth to start using the page transformation tool.

Upgrading Reports

When it came to upgrading reports, then it was a much more troublesome. I actually never found any way to upgrade the RoleTailored Part of the reports. Yes, there sure is a function to “Create Layout Suggestion”. But if what you really just wanted to was to insert a few new fields in the standard NAV report, then this function should really not be used. The function deletes the existing layout, which in most cases means that all the optimization and layout improvements done manually by Microsoft will disappear.

Additionally most standard reports are loaded with small controls which are hidden when printed with the Classic Client, but used when printed in the RTC. That makes editing the reports even more difficult.

So my conclusion to this was that it was much easier to upgrade all the reports manually! Both in the Classic and in the RTC.

Upgrading documents like Invoices and Order Confirmations was an bigger task. I think I was reading somewhere on the internet, that one should estimate 8-16 hours on upgrading just one document. I was really laughing about that, until I was sitting there and doing it myself. The first Invoice took me almost 20 hours!!! And it wasn’t because Visual Studio was all new for me, as I have been using Visual Studio to maintain this website for years! My next document (a Order Confirmation with an almost identical header) took me almost 10 hours and the additional document reports all took between 6-10 hours.

via Microsoft Dynamics NAV 2009 Upgrades and the RTC Reporting Nightmare – Erik P. Ernst about Navision and the Dynamics Community – Dynamics User Group.

Window Server 2008 & SQL server 2008

Did you know that when you add a new Active directory user as a  Windows Login in Dynamics NAV 2009 SP1 in an environment where Windows server 2008  and SQL server 2008 are installed , the new user is automatically created in SQL server Login? This means that we do not have the issue of manually creating SQL login  for Active directory (AD) users. All that is required appears to be logging  into Dynamics NAV as a Super user and then adding a new AD user to Windows Login and synchronise permissions.

Note: I used Windows server 2008 Enterprise and SQL server 2008 – latest service pack installed on the same box in my test.

Recursive Error: Bill-To Customer

In Microsoft Dynamics NAV >>> Customer Card, a user enters the value of Bill-To Customer No. on the invoicing tab as the Value of Customer No. on the General Tab, the following error is triggered when user to use the customer:

Error message : “You must not specify Bill-to Customer No. in Customer customer no. = [nn]

Solution is to Clear the Bill-to Customer No., this is because Bill-to customer No. can only be defined where it is different from the customer No. in question.

How to apply the 6.0 Hotfix to the existing Demo Install

Usage Scenarios

4.1 You have downloaded the RTM image of Microsoft Dynamics NAV 2009 and want to update it with the Hotfix.

  1. Download the HF package from PartnerSource.
  2. Copy the updated database files into the existing database folders and overwrite the existing databases: Demo Database NAV (6-0)_Data.MDF, database.fdb, and database.fbk.
  3. Overwrite the existing form transformation tool files in the Transformation Tool folder with the updated form transformation tool files.

4.2 You have installed the demo database and want to update it with the Hotfix.

  1. Download the HF package from PartnerSource.
  2. Detach or delete the existing Demo Database NAV (6-0)_Data.MDF.
  3. Attach the updated Demo Database NAV (6-0)_Data.MDF from the HF package as described in the C/SIDE online help. To view the online help, on the Open Database form, click Help. In the Microsoft Dynamics NAV Classic Client Help, in the Open Database topic, click the Microsoft SQL Server Option for Microsoft Dynamics NAV link and then go to step 8.
  4. Overwrite the existing form transformation tool files in the Transformation Tool folder with the updated form transformation tool files.

4.3 You have downloaded the RTM image of Microsoft Dynamics NAV 2009 and want to update it with the Hotfix, and you have already started transforming custom forms to pages.

  1. Export language modules for all pages.
  2. Export forms.
  3. Retransform the forms, including report request forms, in your development database to pages by using the new form transformation tool.
  4. Import pages.
  5. Import language modules for pages.
  6. Retransform the forms in your development database to pages by using the new form transformation tool.
  7. Import the transformed pages and report request pages.
  8. Import the language module into the development database.