[AccessD] Naming Conventions

Absolutely.  It is laziness pure and simple.  The data type tells me what
values should be expected or at least what the developer expected.  I tells
me nothing.

John W. Colby
www.ColbyConsulting.com 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, August 05, 2004 2:14 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Naming Conventions


Byte, Integer or Long?  Any of them can be counters.  Counter is a
non-definitive term for a value, and I object to that kind of coding.  

Charlotte Foust


-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com] 
Sent: Thursday, August 05, 2004 8:23 AM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


Me too, Drew. In my code, anything named i j or k immediately signals that's
all it is, a counter.

A.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com
Sent: Wednesday, August 04, 2004 5:15 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Naming Conventions


What's wrong with:

For I=1 to 50

Next I

?

Drew

-- 
_______________________________________________
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