Not sure there is much of a standard, but the minimum would be:
'Purpose: Avoid division by zero error.
If a function, explain what it returns:
'Return: Result of division, or zero in place of error or null.
If it accepts arguments, an explanation of each:
'Arguments: Num1 = numerator
' Num2 = denominator
If usage is not obvious, give an example of how it is used:
'Usage: Set AfterUpdate event of form to:
' Call NotifyCombos(acDeleteOk)
' and AfterDelConfirm event of form to:
' Call NotifyCombos(Status)
If there is something odd about how the procedure works, you may want to
explain the method:
'Method: Handles #1/1/9999# as last effective date.
If there is somehing odd about what it depends on note that also:
'Dependency: Requires functions from our ExtraLib.mda file.
In a multi-user environment, you may also want to specify the author, though
it may be better to keep each author's work in different modules.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"LoopyNZ" <Lo*****@NOguruSPPAM.net.nz> wrote in message
news:41**********************@news.newsgroups.ws.. .
Hi there,
I'm trying to sharpen up my commenting in my code, partly for my own
sake and partly for any inheritors of my code. I'm particularly
wondering what comments are recommended for the beginning of each
procedure.
Can you point me to a site that gives advice on good commenting style,
or post some pearls of your own wisdom? My searches in the
newsgroup/mvps.org/google didn't go too well - searching for "comments"
casts the net rather too wide! :-)
