[AccessD] Naming Conventions

LOL!  I hear that!  I've never had one quite that long, but I've had
some that performed all sorts of exotic calculations using i, j, k,
etc., declared and populated by other calculations earlier in the
routine.  Oh, and don't forget the GoTos that threaded themselves
throughout. :-{

Charlotte Foust


-----Original Message-----
From: Colby, John [mailto:JColby at dispec.com] 
Sent: Tuesday, August 10, 2004 11:36 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


>it occurs to me "dim i as integer" at the start of a loop might solve 
>the
"what type is it"

It would of course (for that area of the code).  It's considered bad
practice to dim variables in the middle of code for obvious reasons.
Plus if the code that I is used in is a page long, you are right back to
"what the heck is i".

I am particularly sensitive to this because a few years back I inherited
the typical "database from hell"  One of the central routines was a
function that was literally 6 feet long when printed and laid on the
floor.  Of course I carved it up into functions but trying to read the
original was just... well... hell.

JWC

-----Original Message-----
From: Hale, Jim [mailto:Jim.Hale at fleetpride.com]
Sent: Tuesday, August 10, 2004 3:02 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


Do you always dim your variables at the top of the routines? I got in
that habit sometime ago but it occurs to me 
"dim i as integer" at the start of a loop might solve the "what type is
it" issue.

Jim Hale

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