[AccessD] TOP FIVE MOST COMMON VBA ERRORS AND THEIR SOLUTIONS

Rocky Smolin rockysmolin at bchacc.com
Sun Mar 15 00:41:22 CDT 2015


How do you mark it as default - on 2003?  I never found a setting for that.

R
 

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Gustav Brock
Sent: Saturday, March 14, 2015 2:04 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] TOP FIVE MOST COMMON VBA ERRORS AND THEIR SOLUTIONS

Hi Susan

Really? I would say that Option Explicit is mandatory - considering that it
can be marked as default, has zero negative effects, but will save you - and
indeed a beginner - for endless trouble.

/gustav

________________________________________
Fra: AccessD <accessd-bounces at databaseadvisors.com> på vegne af Susan
Harkins <ssharkins at gmail.com>
Sendt: 14. marts 2015 21:42
Til: Access Developers discussion and problem solving
Emne: Re: [AccessD] TOP FIVE MOST COMMON VBA ERRORS AND THEIR SOLUTIONS

Well...

I disgree with part of 5) -- some of that stuff is beneficial when you start
adding on and enhancing, changing... why take them out? Well, the
Debug.Print anyway... that's just routine for me and I see no reason to take
them out. They come in handy at all stages of the project.

Option Explicit is a choice. I think it's convenient, but it's a choice.

Susan H.
--
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