If you read Validating Data #3: Cascading VALIDATEs you know by now that a VALIDATE call comes with a price. So where possible the programmer should diminish the number of VALIDATE calls. Or “… to avoid the validate statement when populating records …”, as Marije Brummel puts it in one…
At the time that I did write my initial post on the question Should I transform reports on NAV 2009? SP1 was not yet released for the next batch of countries after the first release of SP1 last August, i.e. for Belgium (BE), Norway (NO), Sweden (SE), … So I could…
John Daskalakis provides some useful information on his blog post SQL Server 2008 Express: the free database engine from Microsoft. Didn’t want to deny you this one [;)].
Joining dynamicsuser.net recently I started writing my blogs to share my NAV experiences with you. So I thought I could spend a couple of posts on some of NAV’s undocumented features. Greenhorn-me just sad down and wrote, not taking much time to investigate the load of posts on dynamicsuser.net. It was not long…
In my post Validating Data #2: Using VALIDATE I addressed the issue of how to validate code entered data by using the field method VALIDATE. In my notes, however, I mentioned that a VALIDATE call comes with a price. This is what this post is about and how to make the cost…