Confused with names!!!!

DaniBoy

Registered User.
Local time
Today, 13:54
Joined
Nov 18, 2001
Messages
174
Hello,
I am kind of confused with the naming convention on fields. When I'am creating a table do I need to put txtName for the field or just Name? Is it a good idea or I only need to do that on my forms and reports with unbound fields!!?

DaniBoy
 
Its a good idea to alwasy place txt infront of the name.. It will save you when your writing code.. Now if its a bound text feild I usually like to just keep it the name of the column but thats just a preference..
 
Dani

The Leszynski Guidelines for Access is the most commonly used naming convention for Access objects. These Guidelines suggest that all objects should have a descriptive tag, placed at the start of the object name.

Note: It is suggested that the choice of naming convention is not as important as making sure that you do implement 'A' naming strategy. Which one is purely a personal preference.

If you decide to implement a naming strategy, ensure that this is carried on right throughout your database. Either apply one or don't but DO NOT do half and half.

HTH

Graham
 
Your table names should NOT have txt in front of them. It isnt wrong to do so..but you want to be very careful with names in tables in case other developers use your application. You may also migrate to another rdbms later on in the future. Your controls should have txt placed in front of the name. This can be true for bound / unbound..it really doesnt matter.

Example:
Table:
Customers

CustomerName
CustomerAddress
CustomerPhone
....
....

Form:
frmCustomers
With say text box fields such as:
txtCustName
txtCustAddr
...
etc.

Jon
 
Since I have a universal validation function I prefer to go the other way
In the table fldCustomerName becomes CustomerName on the form
 
Rich,

ALways making it more interesting than what it is :-p.
You just got to be different huh ;)
JOn
 

Users who are viewing this thread

Back
Top Bottom