Difference between revisions of "Microsoft Access VBA Naming Conventions"

Latest revision as of 16:26, 7 April 2011

Please read the vb24.net Article about Naming Conventions.

@@ Line 2: / Line 2: @@
 [[Category:Conventions]]
 == General ==
-As novice developer you usually define names for constants, variables and methods as they occur;
+Please read the [http://wiki.vb24.net/index.php?title=Naming_Conventions vb24.net Article] about Naming Conventions.
-you look at a problem, think of a function, add some parameters and that's it.
-After a few years of coding&mdash;especially once you are forced to refactor some of your legacy
-coding&mdash;you will realize that the code is hard to read; it somehow feels "inconsistent".
-Also during normal development you will notice that you keep stumpling upon the same issues again
-and again: you're trying to access variables, which are not accessible, you try to use a variable
-for a text value and run in to an error as it has been defined for numbers: the list of little
-annoyances which are implied when not sticking to consistent conventions is long&mdash;add your
-favourite annoyance here.
-The naming conventions depend on the language you are using, but for VBA it is common conviction
-to use either the [http://www.xoc.net/standards/rvbanc.asp Reddick VBA Naming Conventions] or the
-[http://en.wikipedia.org/wiki/Leszynski_naming_convention Leszynski VBA Naming Conventions], which
-are both versions of the [http://en.wikipedia.org/wiki/Hungarian_notation Hungarian notation].
-The main idea is to prefix everything with a mnemonic for its type.
-== Code ==
-*
-== Summary ==
-* &hellip;