[AccessD] VBA Field Names - Curiosity Question

<<And don't get me started on the danger of globals.>>

  I've used globals since day 1 with Access; have never had a problem.

  It's sloppy programmers that write sloppy code that's the issue.  There's
nothing inherently wrong with globals from my viewpoint.   They serve a
purpose and like anything they work fine when used properly.

  It's like the age old admonishment never to use a goto statement.   You
can use goto to your hearts content and still maintain well structured code.
It's a sloppy programmer that ends up with spaghetti code.

Jim. 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Tuesday, July 02, 2013 09:00 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] VBA Field Names - Curiosity Question

Sorry Brad, but adherence to disciplined naming conventions make a HUGE
difference towards ease of maintenance.

Especially critical : Use of Globals !!
And don't get me started on the danger of globals.

> Examples -
> 01 Part-Number   PICTURE X(30).
> 01 Part-Cost    Comp-3    PICTURE 9(05).
>
>
> In VBA examples, I see most people using prefixes such as Str, Lng,
> Dat,
> Etc.
>
> I have never quite understood why people do this when working with VBA
> while I believe that very few people did this in the COBOL realm.
>
> In COBOL we would simply look at the Picture clause in the field name
> definition.  This would be the equivalent of looking at the DIM
> statement.
>
> Again, this is just a curiosity question.
>
> Thanks,
> Brad


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