[AccessD] Naming Conventions

I'm talking about those too.  When you're working in code and you can't
tell by the name of the object what it is, you have to backtrack and
figure it out.  In the database window, you can tell by the tab group,
but you don't have that luxury in code, so debugging code that refers to
opening a recordset on an object named January causes a little trip back
to the DB window to see what you're dealing with.

Charlotte Foust


-----Original Message-----
From: Susan Harkins [mailto:ssharkins at bellsouth.net] 
Sent: Wednesday, August 04, 2004 12:31 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


I'm just talking about the actual object name abbreviations Charlotte.
;) 

Susan H. 

I hope they do.  I had to when I was learning to use a naming
convention. It's a rite of passage for developers.  

One of the things a new developer needs to learn is how to write
standardized code that someone else can decipher.  Unless they're
experienced, their code is going to need a lot of revision over time,
and they'll save plenty of time for themselves and others down the road
if no one has to struggle to figure out what those objects and variables
are. When I have to deal with code that uses variables like i, j, k, l m
or objects like ThisOne, ThatOne, TheOther, I want to beat someone to a
bloody pulp for winging it.  On the other hand, if someone uses
prefixes, I may be baffled by a few of them the first time I see them,
but it won't take long to learn to translate.

Charlotte Foust

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