[AccessD] Class Rebuttal was: Basic Unbound Form ...

Huh?  What are you declaring globally?  You raise an event from the
class and sink it in the other objects.  What does a global have to do
with that?


Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
DWUTKA at marlow.com
Sent: Monday, June 12, 2006 5:25 PM
To: accessd at databaseadvisors.com
Subject: Re: [AccessD] Class Rebuttal was: Basic Unbound Form ...

A class object with custom events.  If you want multiple objects to
'see'
that/those event(s), then you have to declare it globally.

Putting it as a property of a form and keeping that form open is just a
hackneyed way of creating a global variable. (And is pretty stupid,
because if that form isn't needed, it's a waste of resources to keep it
open for a class that could be kept open on it's own.)


Drew

-----Original Message-----
From: Josh McFarlane [mailto:darsant at gmail.com]
Sent: Monday, June 12, 2006 4:18 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Class Rebuttal was: Basic Unbound Form ...


I'd be interested in seeing this instance where an unprotected global
variable has to exist.

Josh