[AccessD] Naming Conventions

John W. Colby jwcolby at colbyconsulting.com
Thu Aug 12 20:59:08 CDT 2004


Well this is good to know because I can get rid of the timer if needed.

John W. Colby
www.ColbyConsulting.com 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert Gracie
Sent: Thursday, August 12, 2004 8:17 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Naming Conventions


John,
 I have been dealing with this for over 4 months, and through some serious
testing I discovered if I shut down the timer, the problem went away, never
to occur again. So that lead me to think that there was something failing or
too complex about the code running in the timer. So I ran the timer to
"count" and the problem would reoccur.

 Extraordinarily frustrating!!!


Robert Gracie
www.servicexp.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of John W. Colby
Sent: Thursday, August 12, 2004 6:51 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Naming Conventions


May I suggest, "lost cause"?

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Francisco H Tapia
Sent: Thursday, August 12, 2004 5:07 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Naming Conventions


DWUTKA at marlow.com wrote On 8/11/2004 1:40 PM:

>These are the after effects of someone's 'deemed' best practices.  If I 
>had a contract job, like the one you discussed below, I would do as the 
>client asked.  But when developing other software, which did not have 
>such client restraints, then I would use the method that I work the 
>fastest in, and find the most convenient to use.  That saves my clients 
>time and money.
>
>It's not lazy, in fact, you could say that you're being lazy, in 
>applying one clients 'demands' on all of your clients, so that you 
>don't have to change mindsets. <Grin>
>
>
While everyone on the list will agree that i, l and k are all simply just
integer or long counters, and could be used interchangeably... it also isn't
a big deal to be explicit and say lngRankCnt or lngRankCount, the fact that
it took you all of a .001 seconds to type out the extra characters is
negligable... and in fact when reviewing your code for logic you'd spot the
variable name and explicitly know what the heck it was ment to do.

--
-Francisco


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






More information about the AccessD mailing list