Re: Option Explicit

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
    ... Is it really worth to put Option Explicit? ... usenet at dfenton dot com http://www.dfenton.com/DFA/ ...
    (microsoft.public.access.formscoding)
  • Re: minutes arent minutes?
    ... Niek cited your own routine as a perfect example of why you should always ... Always use Option Explicit ... worth the trouble. ...
    (microsoft.public.excel.programming)
  • Re: Option Explicit
    ... Warrio wrote: ... I became aggressive when I saw the people using Option Explicit ... to post to a discussion group slam your fingers in a drawer until the urge ... Rick Brandt, Microsoft Access MVP ...
    (microsoft.public.access.formscoding)
  • Re: after running script, wscript stays in memory
    ... :: Michael Harris (MVP) wrote: ... However, if he's not using Option Explicit, it probably wasn't an issue. ... while I was not using Option Explicit, I did put dim fso back. ...
    (microsoft.public.scripting.vbscript)
  • Re: return to where it was
    ... just a learner here but find it really interesting. ... "Helmut Weber" wrote: ... > Option Explicit ... > Helmut Weber, MVP ...
    (microsoft.public.word.vba.general)
Loading