[AccessD] Goodbye Leszynski/Reddick?

Tony Septav TSeptav at Uniserve.com
Wed Jan 21 15:26:01 CST 2015


Hey All
Never used the Leszynski/Reddick format. In my many many years of developing
applications I always used the James/Robiniwisk format. Always worked for
me.

Tony Septav
Nanaimo, BC
Canada

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Dan Waters
Sent: January-21-15 11:35 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Goodbye Leszynski/Reddick?

boolean -> bln 

I like keeping all my prefixes at three letters.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Wednesday, January 21, 2015 10:30 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Goodbye Leszynski/Reddick?

I've continued to use the LRNC convention because I've worked with a suffix
convention and found that it had as many problems as a prefix convention.
LRNC works nicely for me, so I'll be sticking with it.  I have softened a
bit to sometimes use "b" as a boolean prefix, but that's about it.

Charlotte

On Wed, Jan 21, 2015 at 7:34 AM, Salakhetdinov Shamil <mcp2004 at mail.ru>
wrote:

>  HI Gustav --
>
> I have also abandoned LRNC in VBA for quite some time now (and I was a 
> strict "LRNC-adept" in 1990-es). The naming conventions I'm using for 
> VBA look similar to yours but for local variables and for functions'/subs'
> parameters, private subs,functions, properties I'm using lowercase 
> letters in the beginning, and I'm using 'm_"  prefix  for (class) 
> module level variables.
>
> Thank you.
>
> -- Shamil
>
>
> Wed, 21 Jan 2015 12:44:41 +0000 from Gustav Brock <gustav at cactus.dk>:
> >Hi all
> >
> >I had to write a new VBA project from scratch, and given how you
> conventionally program in C# and that Microsoft never has applied the 
> Leszynski/Reddick naming convention (just study the parameter names of 
> the built-in functions), I thought it might be time for a change, if 
> for nothing else to type less.
> >
> >So I did, and I felt well. Now Key can be the name (string) of a key,
> Keys an array of keys, and Value the value of a key, and 
> DataCollection is a collection of data.
> >
> >Much to my surprise, having used Leszynski/Reddick "always" it didn't
> cause any problems to me - in fact I find the code just a little bit 
> easier to read.
> >That may be me, and we all have our preferences, but have a look and
> judge for yourself:
> >
> >     https://github.com/CactusData/VBA.CVRAPI
> >
> >Now, this is code only - no tables, no queries - and that may be 
> >where
> trouble is; it is very convenient from the name alone to know whether 
> you deal with a table or a query, even though a table and a query 
> cannot share the same name.
> >I've seen, that in T-SQL you often prefix views with a V, so Customer 
> >is
> a table and VCustomer is some query/view of table Customer. So a 
> simple prefix of Q for query names could be used. I haven't sorted that
out yet.
> >
> >/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
>
--
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


-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5645 / Virus Database: 4260/8968 - Release Date: 01/20/15



More information about the AccessD mailing list