[AccessD] Naming Conventions

No, we're not and it's probably my fault.  

I'm on the fence about abbreviations, as opposed to tags or prefixes.
We use Rpt to abbreviate "report" in our object names, like
"frmDailyRpt", and I'm lazy enought to prefer that to "frmDailyReport",
but as long as they're consistent and readable, I'm OK with them.  On
the other hand, "rptDailyRpt" would look silly, so we use
"rptDailyReport"!  Either way, it's readable.  It's the ambiguous
abbreviations that are crazy-making:  Dat (is that data or date or a
typo or something I haven't thought of?), Wk (is that week or work or
wok or someone's initials?), etc.  That's where it is up to the company
to determine the standards to make sure they're consistent.

Charlotte Foust


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


Are we talking about the same thing? I'm not talking about omitting the
prefixes -- I'm talking about  abbreviating Customer, Invoice, Names,
Employees, etc... So instead of 

frmEmployees, you might have frmEmp 

You'd need a convention for the convention -- which is OK -- companies
should do what works, but for the individual? Nah... unless that's what
works for him/her. JC was complaining about developers that don't
abbreviate, and personally, I'd find it a pia. If I had to take over an
app full of frmEmp's I'd be annoyed with the convention myself. I'd much
rather deal with full words. 

Susan H. 

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
-- 
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

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