[AccessD] Option Explicit Statement

I always use Option Explicit because, even though I declare my variables, if
I misspell a variable name it catches it on the compile instead of me having
to search out why the program failed.  I don't know of any reason why you
wouldn't want to use it.  

Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com


-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Keith Williamson
Sent: Thursday, January 18, 2007 7: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

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.13/634 - Release Date: 1/17/2007
4:45 PM