In the Debug option of the VBA window there's an option to compile the
project. What exactly does this do and what's the point in it?
In the Debug option of the VBA window there's an option to compile the
project. What exactly does this do and what's the point in it?
Compiling the project checks that the syntax is correct and that the
variables are correctly typed in (that is, if you used Option Explicit,
which you always should.) Sort of checking for errors prior to running the
macro.
HTH,
Bernie
MS Excel MVP
"cdb" <[email protected]> wrote in message
news:[email protected]...
> In the Debug option of the VBA window there's an option to compile the
> project. What exactly does this do and what's the point in it?
So should you compile after every change you make to check it's not incorrect
anywhere?
"Bernie Deitrick" wrote:
> Compiling the project checks that the syntax is correct and that the
> variables are correctly typed in (that is, if you used Option Explicit,
> which you always should.) Sort of checking for errors prior to running the
> macro.
>
> HTH,
> Bernie
> MS Excel MVP
>
> "cdb" <[email protected]> wrote in message
> news:[email protected]...
> > In the Debug option of the VBA window there's an option to compile the
> > project. What exactly does this do and what's the point in it?
>
>
>
It depends on how much you've changed your code and how critical the
application is. Also remember that it doesn't test your code to make sure
that it actually does what you want - no compiler can do that. All it does
is make sure your have your Next's and End if's and all that...
HTH,
Bernie
MS Excel MVP
"cdb" <[email protected]> wrote in message
news:[email protected]...
> So should you compile after every change you make to check it's not
incorrect
> anywhere?
>
> "Bernie Deitrick" wrote:
>
> > Compiling the project checks that the syntax is correct and that the
> > variables are correctly typed in (that is, if you used Option Explicit,
> > which you always should.) Sort of checking for errors prior to running
the
> > macro.
> >
> > HTH,
> > Bernie
> > MS Excel MVP
> >
> > "cdb" <[email protected]> wrote in message
> > news:[email protected]...
> > > In the Debug option of the VBA window there's an option to compile the
> > > project. What exactly does this do and what's the point in it?
> >
> >
> >
OK, will bear this in mind.
Cheers
"Bernie Deitrick" wrote:
> It depends on how much you've changed your code and how critical the
> application is. Also remember that it doesn't test your code to make sure
> that it actually does what you want - no compiler can do that. All it does
> is make sure your have your Next's and End if's and all that...
>
> HTH,
> Bernie
> MS Excel MVP
>
> "cdb" <[email protected]> wrote in message
> news:[email protected]...
> > So should you compile after every change you make to check it's not
> incorrect
> > anywhere?
> >
> > "Bernie Deitrick" wrote:
> >
> > > Compiling the project checks that the syntax is correct and that the
> > > variables are correctly typed in (that is, if you used Option Explicit,
> > > which you always should.) Sort of checking for errors prior to running
> the
> > > macro.
> > >
> > > HTH,
> > > Bernie
> > > MS Excel MVP
> > >
> > > "cdb" <[email protected]> wrote in message
> > > news:[email protected]...
> > > > In the Debug option of the VBA window there's an option to compile the
> > > > project. What exactly does this do and what's the point in it?
> > >
> > >
> > >
>
>
>
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks