[AccessD] Missing references

I haven't thought about this much but I'll cast a vote anyway.  Seems like
sometimes when I declared variable in a procedure I got into some kind of
scoping problem.  So I always Dim everything at the top of the module, group
them by type, and never use a variable  for more than one specific purpose.
There easy to find(Ctrl-Home), easy to see.  

Rocky


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Friday, February 16, 2007 4:08 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Missing references

On 16 Feb 2007 at 10:39, JWColby wrote:

> Actually dimensioning a variable of any kind down in the middle of 
> code is considered bad practice anyway.

It used to be.  There seems to be a growing trend towards "decentralisation"
rather than "consolidation" of declarations.

Now we have "Block Scoped variables" in  VB.Net which *have* to be declared
in the middle of code and many MS code examples now declare all variables
immediately before first use. 

Anyone for another round of Bound/Unbound or Surrogate/Natural et al which
we're at it?  :-)





-- 
Stuart


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

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.441 / Virus Database: 268.18.0/689 - Release Date: 2/15/2007
5:40 PM