Wichtige Region- und Sprach-Einstellungen für NAV 2009 R2 NAV 2009 R2 ist nicht Unicode kompatibel. Dadurch entstehen immer wieder Probleme, dass Zeichen - vor allem Sonderzeichen - im Roled Tailored Client und auch im Classic Client falsch dargestellt werden. Eine Mischung verschiedener Sprachen...
Posted to
German NAV Developers Blog
on 2012-9-12
Filed under: NAV 2009 SP1, NAV 2009, NAV 5.0 SP1, RTC, NAV 5.0, NAS, NAV 4.03, NAV 4.02, NAV 4.01, NAV 2009 R2, Native Server, NST, NAV 4.0 SP3, WebService, NAV 4.0 SP2, NAV 4.0 SP1, NAV 2013
In August 2006 after I just started in my job at ISS I wrote about my worries about Finding the right model for our global Microsoft Dynamics NAV solution. Since then 2.5 years has gone by, so I thought it was on time to write a little about what has happened since then. One Global Database The model...
Posted to
Erik P. Ernst on Microsoft Dynamics and Navision
by
Erik P. Ernst
on 2009-1-5
Filed under: infrastructure, Citrix, Thailand, global database, global core, ISS, Dynamics NAV, Philippines, Reporting Services, Mexico, India, Taiwan, NAV 4.0 SP3, BI, NAV 5.0, Project Management, International Projects, Implementation Methodology, Multi-Site, Polan, Japan
My first full year (January-December)of writing on my blog has passed. When I saw this post on the "NAV Developer's blog", I just thought: "hey, that's a good idea to end this year of blogging. Let's make an overview of my blog as well". And here it is. I was quite surprised...
Posted to
Waldo's Blog - Microsoft Dynamics NAV
by
waldo
on 2008-12-24
Filed under: Development, Dynamics NAV, Philosophy, Installation, Conference, Diary, SQL Server, MVP, NAV 4.0 SP3, NAV 6.0, NAV 5.0, NAV 4.0, NAV 5.0 SP1, NAV 2009, Off Topic, Belgian Dynamics Community, Platform Updates, What impact does my C/AL have on SQL, Windows Server, SQL Server 2008, Convergence, Outlook, Sharepoint, Upgrade
This is an important message for everyone using this hotfix. A bug was introduced causing messages and errorboxes to maintain locks. This issue was also in 3.70 and solved in build 19868 back then. I won't get emotional about this bug but dissapointed describes my feelings best. Please read this...