2008

Today, I got an e-mail from a reader of this blog, who asked me to help them with an actual problem on a project. Their customer is a small manufacturing customer in textile vertical. Whenever they calculate consumption, quantities for certain items get rounded to full numbers.

Code is boring. It is geeky. And it’s ugly, too. In C/AL it is especially ugly. While contemporary development tools come with all sort of gizmos which make coding easier, such as color-coding, auto-completion, refactoring, etc., C/AL editor seems like having awaken from a thousand-year sleep.

Today I got a comment from another soul out there, spending their time blogging about Microsoft Dynamics NAV. I’ve immediately put the link to my blogroll, and it really deserves it, because it is the best blog on the topic I’ve seen so far.

There is only one way to abort a user action in Microsoft Dynamics NAV: by using the ERROR function. This function essentially stops the execution of all code, and prevents completion of the user action, whatever such action might be. One of typical situations where ERROR is used to prevent user action is during validation of a new value in a field.

When Navision Attain attained it’s new name, Microsoft Business Solutions-Navision (the one before the current one), many other things changed as well. Good ol’ main menu was gone. Forever. Main menu was a mighty beast, one of the stronger points of Navision’s user interface at the time.

Whoa, this has been a looooong pause. If you come across some presentation, rhetoric or speach theory, most of them agree on an idea that it’s not the words that make a speach a of art, but the pauses. If the same applies to blogging, I must be quite an artist.