[AccessD] Option Explicit Statement

Keith,
Unless you are a glutton for punishment, this is a "must do" practice. When
I work on anything where it hasn't been used the first thing I do is add it
to all modules. Just one time you have a typo (and I have plenty of them)
which causes a problem and you'll know why :o)

John

PS: There are some tools out there that will do this for you.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Keith Williamson
Sent: Thursday, January 18, 2007 9:30 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Option Explicit Statement

My database performance analyzer is recommending I use Option Explicit
Statements in my two main forms.  I understand the benefits of doing so,
from a programming error recognition standpoint.  Is there any benefit from
a performance standpoint?  I pretty much always declare my variables
anyway...so I don't really see a benefit there (no variants in my
programming.)

 

Any ideas?

 

Regards,

 

Keith E. Williamson | Assist. Controller| kwilliamson at rtkl.com

RTKL Associates Inc. | 901 South Bond Street | Baltimore, Maryland
21231-3305

410-537-6098 direct | 410-276-2136 fax | www.rtkl.com <http://www.rtkl.com/>


 

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