[AccessD] Global Vars (was Ambiguous Name)

It's simple to do than.  Just avoid putting  "myGlobal = ..."  in any code outside of module as a 
matter of policy.

-- 
Stuart

On 20 Sep 2011 at 13:28, jwcolby wrote:

> The nice thing about properties is that they can be set (modified) in
> the module but read-only from outside of the module.  It is impossible
> to do that with globals.
> 
> John W. Colby
> www.ColbyConsulting.com
> 
> On 9/20/2011 1:12 PM, Mark Simms wrote:
> > I'm not totally against them, but lately I've been tending towards
> > the Public Property, the value of which can be easily
> > traced/debugged. Interestingly, MZTOOLZ has a function to do just
> > that: convert globals to properties.
> >
> >
> >> -----Original Message-----
> >> From: accessd-bounces at databaseadvisors.com [mailto:accessd-
> >> bounces at databaseadvisors.com] On Behalf Of Jim Dettman
> >> Sent: Tuesday, September 20, 2011 12:27 PM
> >> To: 'Access Developers discussion and problem solving'
> >> Subject: Re: [AccessD] Global Vars (was Ambiguous Name)
> >>
> >> Mark,
> >>
> >>    You should have quoted the second paragraph as well:
> >>
> >> "This narrow-minded attitude of mine can create difficulties when
> >> trying to share data between forms in a single application."
> >>
> >>    He goes on to say there are lot's of solutions to that problem
> >>    (which
> >> is
> >> true), but that doesn't apply that global's should not be used or
> >> do not have a place in Access development.
> >>
> >> Jim.
> >>
> >> -----Original Message-----
> >> From: accessd-bounces at databaseadvisors.com
> >> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark
> >> Simms Sent: Tuesday, September 20, 2011 11:46 AM To: 'Access
> >> Developers discussion and problem solving' Subject: Re: [AccessD]
> >> Global Vars (was Ambiguous Name)
> >>
> >> 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
> >>
> >> --
> >> 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
>