[AccessD] VBA Field Names - Curiosity Question

Global values help me a lot.  In almost all cases I set the value as the app
starts, and in only one case out of about 50 those values are never changed.

Also, EverythingAccess.com has a new version, V3, of their product
vbWatchdog.  With this version you don't necessarily lose the value of
Globals when you have an error.  Go here:
http://www.everythingaccess.com/vbwatchdog/changesinv3.htm, scroll down to
Global Error Trap improvements.  I've been using this product for several
years and am very happy with it.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
Sent: Tuesday, July 02, 2013 8: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