A97: Is there a way to exclude certain modules from being compiled?

[MLH]

If I test the integrity of my code, opening a module, clicking
Debug, Compile All Modules, the process stops at the first
occurrence of a coding error. Can I skip that and go on
somehow (you know, if the err occurs in a form module
I'm testing but don't wanna fix right now)?

How about a Debug, Compile All Modules Except For...
???

[polite person]

On Sun, 24 Jul 2005 08:05:00 -0400, MLH <CR**@NorthState.net> wrote:

If I test the integrity of my code, opening a module, clicking
Debug, Compile All Modules, the process stops at the first
occurrence of a coding error. Can I skip that and go on
somehow (you know, if the err occurs in a form module
I'm testing but don't wanna fix right now)?

How about a Debug, Compile All Modules Except For...
???

Hi
look up conditional compiling (or conditional compilation) in help.

I have sometimes used this when I have similar code in Access and VB, or for DAO and ADO.

[MLH]

Thank-you, Polite Person. Although it was not what I really
would like to have seen, it made for interesting reading and
I'll play with it in the future.

[polite person]

On Sun, 24 Jul 2005 08:45:57 -0400, MLH <CR**@NorthState.net> wrote:

Thank-you, Polite Person. Although it was not what I really
would like to have seen, it made for interesting reading and
I'll play with it in the future.

You're quick at replying!
I'm watching the F1 race and made my post during one of the adverts

[David W. Fenton]

MLH <CR**@NorthState.net> wrote in
news:6l********************************@4ax.com:

If I test the integrity of my code, opening a module, clicking
Debug, Compile All Modules, the process stops at the first
occurrence of a coding error. Can I skip that and go on
somehow (you know, if the err occurs in a form module
I'm testing but don't wanna fix right now)?

How about a Debug, Compile All Modules Except For...
???

Compile compiles all *open* modules, and all modules on which those
modules depend.

What that means is that if you have Module1 open and compile it, and
it uses a fuction/sub in Module2, which is closed, but saved in a
non-compilable state, then Module1 won't compile.

There is no getting around this restriction because it's absolutely
necessary.

Why do you have lots of non-compilable code lying around?

If it's because of conversion from Access 2, I wonder why the code
didn't get properly converted in the initial conversion? My
experience with Access 2 conversion to A97 was that it was pretty
simple to correct the parts that didn't compile after conversion --
took about an hour to step through all the code and fix the
problems.

One possible solution would be to move the non-converted code into a
single module, but any code that calls functions/subs in that
non-compilable will not compile.

Fix the code.

Be done with it.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc