[AccessD] Global Vars (was Ambiguous Name)

The point of a global variable is to have a VARIABLE value that can be
accessed from multiple points.

If you want a VALUE available from anywhere, that would be a constant.
A variable's value is meant to change.

So, even if you wrap your global variables inside of a class, you are
still scoping an instance of that class globally, which makes it a
global variable.

Any variable and any scope can be used poorly.

Just throwing my hat into the ring.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller
Sent: Tuesday, September 20, 2011 7:07 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Global Vars (was Ambiguous Name)

I think that I am going to go with JWC's concept of this. Assuming of
course that I have it right, you create a class that houses all the
otherwise global variable, and they are protected by Get/Set methods.
This appears to me the superior way to go. No way you can touch them.
fork with them, without a specific call. No accidents, no side effects.
Good for you, JWC. I think you are right on the money here.

Arthur
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.