[AccessD] Global Vars (was Ambiguous Name)

Horsepucky.

That's just a confirmation of Gustav's statement  that the problem is the programmer, not the 
global.

As a general rule, Global's should be set in only one place, but can read/used anywhere.

They should not be used to carry values which can be modified indiscriminately.  (unless you 
are using them in a mulit-threaded application where they are also useful for passing values 
between threads)

-- 
Stuart

On 20 Sep 2011 at 11:46, Mark Simms wrote:

> Au Contraire....use sparingly at best:
> www.vb123.com/smart/fp/1998-05.pdf
> "they dramatically increase the costs of
> maintaining an application. After all, when you find a bad value in a
> global variable, that value could have been placed in the variable
> from any routine in the application. Thats a lot of code to debug"
> 
> >
> > Nothing wrong with global variables.
> > Trouble is always located at those handling these (the programmer!).
> >
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>