[AccessD] VBA Field Names - Curiosity Question

Tony Septav TSeptav at Uniserve.com
Thu Jul 4 14:59:54 CDT 2013


Hey All
Cut the crap.
Who cares what each of us thinks is right or wrong. If you produce a good
product which you should be doing as a programmer and it is clean and works
the way the client has asked (now I have seen some others pretty S... code,
not on this list) you have done your job. Who cares how other programmers do
their job.  Yes I have looked back at my code and thought "Hey I could do
this better". You deliver the product and smile as  A,B and C have been
completed and you have done your job done as a professional.  Sorry to the
newbies.

Tony Septav
Nanaimo, BC
Canada 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: July-04-13 9:43 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] VBA Field Names - Curiosity Question


 Since I moved away from mini-computers back in the 80's, I haven't used it
except it for one occasion.

 It was for a Bill of Material explosion routine and the choice was use a
goto to loop back up to the top of the procedure or call it recursively.

 I chose the goto because it was clear what was being done, it was faster
because nothing went on the stack, and it was less resource intensive
because I didn't have to declare my level array as static.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Wednesday, July 03, 2013 07:12 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] VBA Field Names - Curiosity Question

Correction:

I haven't actually used a GOTO, other than in ON ERROR GOTO, for ...

:-)

-- 
Stuart 
 
On 3 Jul 2013 at 15:30, David McAfee wrote:

> On Error GoTo MyProcedure_Error  ;)
> 
> 
> 
> On Wed, Jul 3, 2013 at 3:24 PM, Stuart McLachlan
<stuart at lexacorp.com.pg>wrote:
> 
> > Agree, what is the "danger of globals" if you:
> >
> > a.  identify them properly using a naming convention
> > b. use them properly by only writing them in one location and
> > c.  trap errors properly.
> >
> > Same with Goto.  It's a perfectly valid command which does exactly the
> > same as the heavily
> > used assembler JMP,JNE etc instructions.
> >
> > It's "abuse", not "use" that have given these two their bad reputations.
> >
> > (But I haven't actually used a GOTO for many, many years - I've never
> > found a situation yet
> > where there wasn't a "more elegant" solution <g>)
> >
> > --
> > Stuart
> >
> > On 3 Jul 2013 at 9:04, Jim Dettman wrote:
> >
> > > <<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.
> > >
> >
> > --
> > 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: 2013.0.3345 / Virus Database: 3204/6463 - Release Date: 07/04/13



More information about the AccessD mailing list