Re: Option Explicit

Thanks for your quick answer! but sorry I forgot to mention in which way it
would help Access to run my code faster ?

and so far, I'm happy to have the choice to declare or not my variables and
set their type, but I'm ready to change my habits ONLY if it can help my
forms run and load faster (you made your choice, I can have a different one)
....
the main part of my forms performances is dealing with the sql requests and
actions. but how much will I win if I use "Option Explicit" knowing that
today users have 1 to 2 GB processors...

Thanks again!



"Marshall Barton" <marshbarton@xxxxxxxxxx> a écrit dans le message de news:
a89g739u6fojegf43p9l95d59096h0f1fq@xxxxxxxxxx
Warrio wrote:
Sorry if I'm asking a question already asked, but I haven't found a real
answer to my question on Internet...

Is it really worth to put Option Explicit? it would be great if you could
develop your answer!


Strongly recommended.

If you don't use it, then any undeclared variable name you
use will be type Variant and have a value of Null when you
misspell the name you meant to use. Option Explicit will
catch that error immediately so you can avoid a lot of
tedious debugging just to find a typo.

--
Marsh
MVP [MS Access]


.

Relevant Pages

  • Re: Option Explicit
    ... Variants are a psuedo object that must be processed to ... would help Access to run my code faster? ... Is it really worth to put Option Explicit? ... use will be type Variant and have a value of Null when you ...
    (microsoft.public.access.formscoding)
  • Re: Option Explicit
    ... way it would help Access to run my code faster? ... I'm happy to have the choice to declare or not my ... It has to do with catching silly typing ...
    (microsoft.public.access.formscoding)
Loading