A long while back before Navision was bought by Microsoft, they give a manual or booklet on the coding standards. I'm not sure if they still provide that now.
Basically, to follow the Navision standard, use the same "look and feel" as the existing codes.
Hariharanssudan: why don't you just look at the code, f.e. Codeunit 80?
FCP: and does it really help you in any way? Wow, I'm amazed. Charles Simonyi designed H.N. for completely different purposes: notating the purpose of variables and not just simply types. In standard Navision, variables like OldValueEntry and NewValueEntry are a lot closer to the concept of H.N. than f.e. recValueEntry would be.
Do It Yourself is they key. Standard code might work - your code surely works.
Comments
Personally I consider much more “readable” the use of of a prefix for variables of some kind. Is not as important as good comment lines but helps.
I use the following Prefixs
Rec - Record
Unit - CodeUnit
Par – parameter in a function
G – Global Variables
P – Private Variable
Aut - Automation
This is just my personal an example
Basically, to follow the Navision standard, use the same "look and feel" as the existing codes.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
FCP: and does it really help you in any way? Wow, I'm amazed. Charles Simonyi designed H.N. for completely different purposes: notating the purpose of variables and not just simply types. In standard Navision, variables like OldValueEntry and NewValueEntry are a lot closer to the concept of H.N. than f.e. recValueEntry would be.
Do It Yourself is they key. Standard code might work - your code surely works.