kriki: NAV2013

[Blog bot]

I will be trying to blog a little about NAV2013 in the near future.

While I am studying the online help (http://msdn.microsoft.com/en-us/libr...3988(v=nav.70) ) of NAV2013, I sometimes want to comment on some changes and sometimes I wonder about how something works or how it changed.

Lately I have blogged very little, but I hope to change that with my NAV 2013 series. Now that I am really studying trying to really study NAV2013, I want to blog about the changes I find. Most of them are described in the manuals or online help (http://msdn.microsoft.com/en-us/libr...3988(v=nav.70) ) (If you have time, go to that link and read-read-read!) or have been blogged about. But I think it is helpful having a blog to comment on some of the changes.

First remark about NAV 2012 … eh … 2013: After SQL Server 2012, Windows Server 2012, Visual Studio 2012, I have a difficult time writing NAV 2013. Why did Microsoft use NAV 2013 and not NAV 2012? NAV2012 NAV2013 was released in 2012 anyway.

I already found myself writing NAV 2012 a few times…..

One thing I really will have to update is the "How to work with record-variables" (http://www.mibuso.com/howtoinfo.asp?FileID=22). But I will do this after I have some (=a lot) of experience with the changes in NAV2013.

First thing about NAV2013 (and you probably heard/read it dozens of times but I will still repeat it).

Let me use some famous British words for that (words preferably used as little as possible I would say) (I did change some words), but I think they are perfect:

The NAV is dead. Long live the NAV.

Checking Wikipedia (http://en.wikipedia.org/wiki/The_Kin...live_the_King.) I learned something I didn’t know anyway: those words have French origins.

The NAV is dead: no more native DB, no more classic client, no more dataports, no more forms, no more OCX, no more classic NAS, no more C/FRONT (someone used this? I never did).

Long live the NAV: 64-bit service tier, oData, new debugger, new NAS, background sessions, Query object, Unicode, Web Client, ADO instead of ODBC, smart SQL, … , and a lot more (I just mentioned the ones I like most)



Читать дальше