Leszynsky Naming Convention (LNC) and RVBA
We should be absolutely clear that Access does not impose any restrictions about naming of fields/columns or any other element. Following conventions increases readability and the self-documenting nature of the programs developed in Access. If you were to call in expert help at some point in the development of your project, it will be far easier to understand for the external expert if a convention was followed. Within the team, it will make communication very effective and save time during project meetings when development strategies or problems are discussed.
When naming each of the entities, there is a tag added to the name. Tag comes first followed by the name. The tag is a unique two/three letter combination for the type of entity. The tag "tbl" is a good tag when tables are to be used. The "tmp" tag defines temporary tables. Using a "bck" tag is useful for backup tables. A secondary benefit is that Access will keep the tables with the same starting tag together. Thus, the main table, the temporary table, and the back up tables remain together.
The seven types of objects in Access have tags: "db" for database, "tbl" for tables, "qry" for queries, "frm" for forms, "rpt" for reports, "mcr" for macros, and "mdl" for modules. Fields or column names have tags depending on the data type they are supposed house. These are "bin" for binary, "byt" for byte, "cur" for currency, "dtm" for date/time, "dbl" for double precision data, "lng" for long integer, "mem" for memo, "ole" for OLE objects, "sng" for single, "str" for text strings, and "ysn" for yes/no type fields/columns.
These examples are from the LNC. However, the conventions from RVBA also are similar; in these specific cases of column names, there are only slight variations in the tag names.