Drew Wutka
DWUTKA at marlow.com
Wed Sep 10 23:12:23 CDT 2003
You are right, our situations are different, but I do have to deal with
other people's code once in a while. I never have a problem with naming
conventions though, probably due to my own usage of a naming convention. I
never rely on someone's naming convention, it just isn't one of major
concerns. My big issues usually surround extremely poor logic, or poor
techniques. (I can't tell you how many access db's I've been handed where a
form is filtered to the hilt, instead of building a good query to deal with
showing new data.)
Drew
-----Original Message-----
From: William Hindman
To: Access Developers discussion and problem solving
Sent: 9/10/03 7:28 PM
Subject: Re: [AccessD] Naming Convention (was Days Past Due - Grace Period)
...I can ...have ...will :)
...working with my own code is difficult enough using naming conventions
...trying to figure out what someone else intended when they don't use
Reddick and/or don't comment their code/conventions drives me ape ...you
work in a different environment than I do ...I constantly get handed
code
that someone else did, they are no longer available, and no one in the
client's office has a clue ...and most of it isn't written using Reddick
or
comments ...actually most of it would be better off dumped in the bit
bucket
but that's usually not an option ...so, if I'm doing anything other than
a
quick fix, my first task is to standardize the code using naming
conventions
and comments where possible ...all while loudly and inventively cursing
the
bunghole who wrote it :))))
William Hindman
So, then, to every man his chance -- to every man, regardless of his
birth,
his shining golden opportunity -- to every man his right to live, to
work,
to be himself, to become whatever his manhood and his vision can combine
to
make him -- this, seeker, is the promise of America.
-- Thomas Wolfe
----- Original Message -----
From: "Drew Wutka" <DWUTKA at marlow.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Wednesday, September 10, 2003 5:25 PM
Subject: RE: [AccessD] Naming Convention (was Days Past Due - Grace
Period)
> Oh come on, that's not true. You can't possibly say that when you
have to
> work on someone else's code, that if someone used 'strStatus' to
represent
a
> variant, which is going to be a string in all cases except when it's
Null,
> that you would go and rename it everywhere.
>
> I think there is WAY too much fuss about this.
>
> Drew
>
> -----Original Message-----
> From: Charlotte Foust [mailto:cfoust at infostatsystems.com]
> Sent: Wednesday, September 10, 2003 3:39 PM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Naming Convention (was Days Past Due - Grace
> Period)
>
>
> I think the point is that in VBA you would normally use type specific
> prefixes, whatever you may do in ASP. I'm glad you have to maintain
> your code. It would drive me nuts and I'd wind up renaming
everything!
> 8~{
>
> Charlotte Foust
>
> -----Original Message-----
> From: Drew Wutka [mailto:DWUTKA at marlow.com]
> Sent: Wednesday, September 10, 2003 11:51 AM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] Naming Convention (was Days Past Due - Grace
> Period)
>
>
> But why would you change your coding style in a scripted language? In
> ASP, I still use int and str as prefixes, even though everything is a
> variant.
>
> Along those lines, I use int for ALL integers, mainly because I only
use
> an Integer type when absolutely necessary (if an API requires
it...etc.
>
> Drew
>
> -----Original Message-----
> From: Jim DeMarco [mailto:Jdemarco at hshhp.org]
> Sent: Wednesday, September 10, 2003 1:28 PM
> To: Access Developers discussion and problem solving
> Subject: RE: [AccessD] Naming Convention (was Days Past Due - Grace
> Period)
>
>
> ASP is a different animal though isn't it? Scripted code versus
> compiled and all that. Reddick naming conventions specify using "var"
> prefix for variants although we use "v" here (or "var"). Seems
> dangerous not specifying the actual data type in your VB/VBA code.
>
> My 2 cents,
>
> Jim DeMarco
> Director of Product Development
> HealthSource/Hudson Health Plan
>
>
> -----Original Message-----
> From: Drew Wutka [mailto:DWUTKA at marlow.com]
> Sent: Wednesday, September 10, 2003 2:18 PM
> To: 'Access Developers discussion and problem solving'
> Subject: RE: [AccessD] Naming Convention (was Days Past Due - Grace
> Period)
>
>
> Do you write ASP pages? If so, do you prefix all of your variables
with
> var?
>
> Drew
>
> -----Original Message-----
> From: Don Elliker [mailto:delliker at hotmail.com]
> Sent: Wednesday, September 10, 2003 9:20 AM
> To: accessd at databaseadvisors.com
> Subject: RE: [AccessD] Naming Convention (was Days Past Due - Grace
> Period)
>
>
> I don't get it...how do you ever know what the datatype is?? How do
you
> know
>
> when an 'str' is really a string and when it will accept a form
> reference. How about overflows? If you follow that logic, what looks
> like a long, may be an integer. I suppose you can do whatever you
want,
> but if the logic is "I may need to have something else here but I want
a
> string"...then why not (as I believe William suggested) make them all
> variant and leave off the datatype
> 'convention' (not).
> _d
>
>
>
> "Things are only free to the extent that you don't pay for them".-Don
> Elliker
>
>
>
>
>
> >From: Drew Wutka <DWUTKA at marlow.com>
> >Reply-To: Access Developers discussion and problem
> >solving<accessd at databaseadvisors.com>
> >To: "'Access Developers discussion and problem solving'"
> ><accessd at databaseadvisors.com>
> >Subject: RE: [AccessD] Days Past Due - Grace Period
> >Date: Tue, 9 Sep 2003 16:33:06 -0500
> >
> >I don't think I have every prefixed a Variant as var, yet. My logic
in
>
> >my statement is I want a string, so I prefixed it as a string, but it
> >may need to be a variant, so it's declared as a variant.
> >
> >Drew
> >
> >-----Original Message-----
> >From: Gustav Brock [mailto:gustav at cactus.dk]
> >Sent: Tuesday, September 09, 2003 3:24 AM
> >To: Access Developers discussion and problem solving
> >Subject: Re: [AccessD] Days Past Due - Grace Period
> >
> >
> >Hi Drew
> >
> > > .. I left the strStatus argument as a variant, in case it is ever
> > > passed a null
> >
> >Then you should have renamed it varStatus ...
> >
> >/gustav
> >
> >_______________________________________________
> >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
>
> _________________________________________________________________
> Use custom emotions -- try MSN Messenger 6.0!
> http://www.msnmessenger-download.com/tracking/reach_emoticon
>
> _______________________________________________
> 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
>
>
>
************************************************************************
> ****
> *******
> "This electronic message is intended to be for the use only of the
named
> recipient, and may contain information from Hudson Health Plan (HHP)
> that is confidential or privileged. If you are not the intended
> recipient, you are hereby notified that any disclosure, copying,
> distribution or use of the contents of this message is strictly
> prohibited. If you have received this message in error or are not the
> named recipient, please notify us immediately, either by contacting
the
> sender at the electronic mail address noted above or calling HHP at
> (914) 631-1611. If you are not the intended recipient, please do not
> forward this email to anyone, and delete and destroy all copies of
this
> message. Thank You".
>
************************************************************************
> ****
> *******
>
> _______________________________________________
> 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
> _______________________________________________
> 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