Queries Naming Conventions

[Mat55]

I was told I had to do naming conventions, but from what I see I have it correctly done.. examples of some names are

qryCarsBefore1990s
qryRedOrToyota
qryVanToyota

Also, for reports, I have stuff like

reportCarsBefore1990s
reportRedOrToyota
reportVanToyota..

If it helps my tables have like Vehicle, Manufacterer etc, not tblVehicle, and I was told only my qry and reports needed changing.

also, it says stick to a naming convention


What is the proper way to name it? Thanks.

 

[pr2-eugin]

Matt, Naming conventions are for better clarity and understanding, even if you had not said these are tne queries anyone who is dealing with access/ any programming language will understand qry is query. Although it is highly recommended to stick to the proper naming convention; which you have done. It really depends on the individual. If you wish to have the tables as tblVehicles please do so if not no one is going to nail you to the cross..

So chill out, in my view best to have it as tblVehicles.

Good luck and welcome aboard.

 

[jdraw]

Proper is what works for you and doesn't cause errors.
In chapter 3 of this reference material is a discussion of names

This is great resource for Access developers/programmers.
http://www.utteraccess.com/uploads/Crystal/


Here's a naming convention tutorial on the site

http://www.access-programmers.co.uk/forums/showthread.php?t=225837

 

[Mat55]

Matt, Naming conventions are for better clarity and understanding, even if you had not said these are tne queries anyone who is dealing with access/ any programming language will understand qry is query. Although it is highly recommended to stick to the proper naming convention; which you have done. It really depends on the individual. If you wish to have the tables as tblVehicles please do so if not no one is going to nail you to the cross..

So chill out, in my view best to have it as tblVehicles.

Good luck and welcome aboard.

The problem is I got told I have to have proper Naming Convention for Queries, Forms, Reports, and my table field names..

My tables:
Vehicles

Queries:
qryVehicles

Form:
Vehicles

Report:
reportVehicles

So judging on what I wrote it looks like I have it properly done.. but I am being told I dont have Queries Forms and report done correctly..

 

[jdraw]

Does your organization/customer have naming standards?

 

[Mat55]

Lets just say im doing basic/college databases (and naming standards).

I am very confused.. I would give out a full example but I'd prefer to keep it private.. would it matter if I made it all like Vehicles, etc, instead of qryVehicle, frmVehicle etc?

 

[jdraw]

Hmmm
What happens when you have 6 queries related to Vehicles?

 

[Mat55]

Well I mean like..

Vehicles
VehiclesRed
VehiclesMadeThisYear
etc..

I dont know to be honest, I been doing databases for a little while and never has someone told me to fix the naming conventions..

 

[Galaxiom]

There is a simple rule with naming conventions. If your boss tell you that they are necessary then you do them because they said so. Otherwise do what you like.

Personally I find the use of prefixes on everything more a distraction than a help, especially with table field names. The data type of the field or control is just one of its properties.

Another that makes little sense to me is frm and subfrm since the same form object can be used as both.

 

[Mat55]

I been told to choose a naming convention and stick to it. So anyone see anything wrong in my examples above? Am I not being consistent enough?

Also for my table field names I used FirstName, LastName in a lot of my tables, and my field names are also something I need to choose a naming convention for.. any help?

Also I use ID for all my tables, and then for my caption I use for example Vehicle ID so it shows that on the table.. should I just put ID?

EDIT #100: Also I realised if I put Name_ in one table, I put caption (for example) Vehicle Name, I think I should keep it Name.

 

[Galaxiom]

I consider the use of the Caption property in a table field as even worse than using lookups in tables. It makes it very hard to see the actual field name.

The caption might seem handy when you are just using the wizards to create queries and forms but it becomes utterly intolerable when you refer to them in procedures and have to use the actual name of the field.

Keeping tables as explicit as possible is far more important than any naming convention.