Until the release of Microsoft Dynamics NAV 2009 then the technical
architecture behind Dynamics NAV / Navision was a "typical"
client/server architecture, where you had a database server (either the
native Navision server or SQL Server)
and the classic client .
But with the release of Navision 2009 the customers also have the choice of the
new Dynamics NAV Role Tailored Architecture, with the Role Tailored Client, SQL Server and the
Dynamics NAV Server .
The Classic Architecture
is still used by companies on older versions than NAV 2009, and by
companies who doesn't want to use the role tailored client. But the
classic architecture with the classic client is also used for user
administration and development, as these components are still not
available in the Role Tailored Architecture.
The Role Tailored Architecture is used whenever a company want to use the role tailored client or the web services.
The internal architecture in the application and database is
basically the same as it was when Navision was first released in 1987.
Of course many new functions and hereby objects consisting of tables,
forms/pages, reports, codeunits etc. has been added since then, making the architecture a lot more complex.