[AccessD] AccessD Digest, Vol 103, Issue 17

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

I think the interesting question is not where a global is set, but by whom.
If it is not simply read-once, how do you ensure the right party gets to set
the globals?

They should not be used to carry values which can be modified
> indiscriminately...
>

But what if you need to modify globals? What do you do then? It is hard to
write a real Access app that doesn't require global parameter passing, which
requires changing globals.

-Ken