[AccessD] VBA Field Names - Curiosity Question

So I was working with our lead programmer today

He has a master's degree in computer science.

We were working on exporting a cloud report into an excel file. He named
the object, rdlc, variable and report "hierarchy"
On Jul 2, 2013 6:55 PM, "Darryl Collins" <darryl at whittleconsulting.com.au>
wrote:

> Yeah, I would agree with that.  I guess the important thing is not so much
> "what" method you use - there are gazillion different opinions on methods,
> but ensure you are consistent and logical with the syntax chosen.
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com [mailto:
> accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms
> Sent: Wednesday, 3 July 2013 11:00 AM
> 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
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>