[AccessD] Naming Convention (Query SQL correctbutnotvisibleindesign view)

Charlotte Foust cfoust at infostatsystems.com
Tue Dec 28 16:55:11 CST 2004


LOL, of course!  It's irritating to have to live with a convention that
isn't fully rationalized and that the originator isn't yet using because
he's not programming in .Net yet.

Charlotte Foust


-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com] 
Sent: Tuesday, December 28, 2004 1:17 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Convention (Query SQL
correctbutnotvisibleindesign view)


Well.. You and I are the only experts that really matter in our world
right?
;-)

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte
Foust
Sent: Tuesday, December 28, 2004 4:01 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Naming Convention (Query SQL correct
butnotvisibleindesign view)


I agree, John.  Unfortunately, I lost that battle with respect to
objects in our VB.Net environment.  Several "experts" wrote books and
articles insisting that hungarian was dead, so the experts that insisted
it wasn't got ignored.  I HATE having to read the entire name of
something to discover at the end that it's a form, subform, report, etc.

Charlotte Foust


-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com] 
Sent: Tuesday, December 28, 2004 12:26 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Convention (Query SQL correct but
notvisibleindesign view)


Arthur,

That of course is a simple matter of preference, not a matter of one is
inherently better than the other.  In fact I don't much care which is
used as long as something is used.  I do prefer prefixes because the eye
is much faster at finding the beginning of a name than the end of a
name.  Thus if I have a SQL statement with 5000 characters, I can scan
(read) the statement and the objects pop out of every object name.
tblPeople is much easier to determine that it is a table than PeopleTbl,
and even more so when there are 3 or 4 words.  If you are scanning
something looking for a reference to a form or a control, it is just
plain easier to find those objects when the "xxx" is a prefix.

In the end though, for purposes of doing a search using a search tool,
it really truly DOESN'T matter.  tblPeople or PeopleTbl are equally
distinguishable and easily found.  If anything can be named People
(forms, reports, queries, combos, text boxes etc. then we are talking
chaos and an automated search (without an eyeball guiding it) becomes
literally impossible.

Again, it is a matter of opinion whether to use prefixes or suffixes.  I
use prefixes, I have tried suffixes and always went back to prefixes,
but in the end either distinguish the object by type and that is the
most important thing.

John W. Colby
www.ColbyConsulting.com 


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list