[AccessD] Darth Vader calls you

DWUTKA at marlow.com DWUTKA at marlow.com
Tue May 17 19:11:55 CDT 2005


LOL.  Okay Mr. Sith.

Drew

-----Original Message-----
From: John W. Colby [mailto:jwcolby at colbyconsulting.com]
Sent: Tuesday, May 17, 2005 6:18 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Darth Vader calls you


ROTFL.  Tilting at windmills and saving junior programmers from the evil
Darth Vader.  I am honored that I should be elevated to such status, Jedi
Knight and master of evil.  I like it!  I must say though that I always
empathized with Darth.

Come to the dark side.

John W. Colby
www.ColbyConsulting.com 

Contribute your unused CPU cycles to a good cause:
http://folding.stanford.edu/

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of DWUTKA at marlow.com
Sent: Tuesday, May 17, 2005 7:05 PM
To: accessd at databaseadvisors.com
Subject: RE: [AccessD] Global Variable


I guess I'm not seeing the same definition from John, though it was closer
in the last few posts.  Yes, 'bad practice' sends me into a tail spin, when
there is no reason for calling something bad practice.  Declaring a variable
as an Integer IS bad practice.  It is bad practice because even if you think
a variable will never go over 32k, or below -32k, it can, and probably will.
But more importantly, an Integer is a 16 bit variable, and it takes longer
to process an Integer then it does a Long Integer, on a 32 bit system.  The
first reason is a philosophy.  The second reason is a FACT!

I have yet to hear a fact, as to why Globals are 'bad practice'.  What gets
my goat, though, is that this is a forum where developers of all skill level
meet.  If opinions are given as facts, developers who are learning something
new could be hampered by prejudice.  Ever run into an IT shop that refuses
to allow applications to be developed in Access, because 'it's not a
database', or 'it's not secure', or something else, that is just ignorance
repeated through 'tribal knowledge'?  (There is also usually power
involved...and IT shop has more power and control involved when something is
on a server side db.)  That's why I rail on this stuff, because invalid
tribal knowledge can be dangerous!

Drew


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



More information about the AccessD mailing list