Naming Conventions

[Dewey]

This has been bugging me for a while... I understand the benefits of using
naming conventions in Access and, for the most part, the three letter
prefixes used are immediately obvious - tbl = table, qry = query, txt = text
box, etc. When it comes to modules, however, I see similar naming
conventions used by many people but their meaning isn't as obvious to me.

Many people use names such as acbModule or basClassModule. Do the prefixes
'acb' and 'bas' have a specific meaning? Is there a good comprehensive
listing somewhere that explains the rationale behind naming conventions used
in VBA?

 

[Allen Browne]

bas was common in the early days of Access (since the language is BASIC.)

cls is sometimes used for class modules (as distinct from standard modules.)

When developers work as a team on a project, you will sometimes see them
using their initials as the prefix for the module, so that any developer
knows who to talk to if they want to track down how to use one of the
procedures.

 

[Jeff Conrad]

See this area of my Resources page for info on this subject:

http://home.bendbroadband.com/conradsystems/accessjunkie/resources.html#NamingConventions

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html

in message:

 

[Dewey]

Thank you. I read through coding examples on web sites like yours and Access
Junkie's all the time. I never considered the use of initials as a prefix,
so I was beginning to get the impression that there was some grand logic for
the letters chosen in different situations...

 

[Tony Toews]

This has been bugging me for a while... I understand the benefits of using
naming conventions in Access and, for the most part, the three letter
prefixes used are immediately obvious - tbl = table, qry = query, txt = text
box, etc.

And using tbl and qry are actually a big pain in the *ss. I use the
first letter of the subsystem while in the database window to quickly
navigate to that object. For example p for purchasing.

So I've stopped using the object naming conventions quite a number of
years ago. Or rather I never did use them as they just didn't make a
lot of sense to me.

I still do some inside VBA code, it str for String and lng for Long
but even those I find of limited use so I've pretty much stopped that.

Many people use names such as acbModule or basClassModule. Do the prefixes
'acb' and 'bas' have a specific meaning? Is there a good comprehensive
listing somewhere that explains the rationale behind naming conventions used
in VBA?

And I see no reason for these as well.

Also I have my own naming conventions for fields within tables.

Tony's Table and Field Naming Conventions
http://www.granite.ab.ca/access/tablefieldnaming.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm