|
Regina Whipp |
|
The difficult I do immediately, the impossible takes a little bit longer. |
|
In database development it is a good idea to use some sort of naming conventions similar to the ones listed below by Leszynski/Reddick. Why? Because the next Programmer to come along should not have to try to figure out whether my query is a make table or delete query! They shouldn't have to guess whether the form is a main form or a subform. You do not have to use the one below as long as you implement some sort of naming convention. The ones I commonly use are in bold print. |
Naming Conventions |
|
Miscellaneous |
|
When it comes to Table names I like to use comprehensible names, ie…
tblClientProfile tblVendorProfile
I then use the Table names as prefix values for the field names, ie…
tblClientProfile cpClientID (Primary Key) cpFirstName cpLastName etc…
tblVendorProfile vpVendorID (Primary Key) vpCompanyName vpAddress etc…
Doing this serves two purposes for me…
The first, it insures that I do not use any Reserved Words, which Access would not like and I would have to use brackets around, like [Date] and hope Access still didn’t object. Access 2007 gets especially *upset* when faced with a field or table name that uses one of its favorite words..
The second, when reading my code months or even years down the road I know immediately which table the field comes from. |
|
My Table Naming Conventions |