View Single Post
  #2  
Old February 24th, 2006, 07:39 PM posted to microsoft.public.access.tablesdbdesign
external usenet poster
 
Posts: n/a
Default Proper way to name objects..

These are standards that have been around for a while. Most of us with some
experience use some form of these. For instance, I might name my queries:
qsel - Select Queries
qapp - Append
qdel - Delete
qtot - Totals
qxtb - Crosstab
qupd - Update
I think the key is to find a naming convention that means something to you
and try to be consistent. One thing you won't see in my object names is
spaces and punctuation.

Jeff Conrad has some links at
http://home.bendbroadband.com/conrad...ingConventions

One convention that I have found very useful is naming all of my fields
beginning with 3 characters that describe the table. For instance:
tblEmployees
=============
empEmpID autonumber primary key (Always)
empFirstName
empLastName
emp....

tblEmpTimeSheet
================
etsETSID autonumber primary key
etsEmpID link to tblEmployees.empEmpID
etsWorkDate
etsPrjID link to tblProjects.prjPrjID
etsWkTID link to tblWorkTypes.wktWkTID
ets...

--
Duane Hookom
MS Access MVP
--

"Mell via AccessMonster.com" u18304@uwe wrote in message
news:5c5f2069e09b2@uwe...
I have been told that if you don't name your tables, queries, forms &
reports
like below than you did not build the db properly? Do these abbreviations
have to be put in front of the name to be policitally correct as a good
developer?


1. TABLES: tbl
2. QUERIES: qdf
3. FORMS: frm
4. REPORTS: rpt

Any suggestions would be greatly appreicated.

--
Message posted via http://www.accessmonster.com