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

[Susan Harkins]

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.

On Sat, Mar 14, 2015 at 4:36 PM, Rocky Smolin <rockysmolin at bchacc.com>
wrote:

>
>
>
> http://www.lugh-sci.com/blog/top-five-most-common-vba-errors-and-their-solut
> ions?utm_content=buffer61fac
> <
> http://www.lugh-sci.com/blog/top-five-most-common-vba-errors-and-their-solu
>
> tions?utm_content=buffer61fac&utm_medium=social&utm_source=linkedin.com&utm_
> campaign=buffer#blogue>
> &utm_medium=social&utm_source=linkedin.com&utm_campaign=buffer#blogue
>
> Of course, this isn't really necessary for us. :)
>
> r
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>