Hi folks,

My program consists of 197 .xls files in 5 sub-folders. 134 of these files
contain programming and macros.

The different files interact with each other in various ways, with different
macros opening and closing other files at different times, and data being
added to, removed from, or used by various files by macros when under the
control of various other files.

Anyway, In the Debug menu of the VBA Editor I see the 'Compile VBA Project'
command. My understanding of compiling is that it compresses the code files
to remove various elements used when creating the program, and make the
program ready for release. Is this correct?

Do I need to compile my program before release, and if so, do I need to
compile each .xls file individually?

Thanks.

Pretty good answer (and explanation) here:

http://www.vbaexpress.com/forum/showthread.php?t=9772


"dim" <(E-Mail Removed)> wrote in message
news:C8F576EF-EDF9-4050-B970-(E-Mail Removed)...
> Hi folks,
>
> My program consists of 197 .xls files in 5 sub-folders. 134 of these files
> contain programming and macros.
>
> The different files interact with each other in various ways, with
> different
> macros opening and closing other files at different times, and data being
> added to, removed from, or used by various files by macros when under the
> control of various other files.
>
> Anyway, In the Debug menu of the VBA Editor I see the 'Compile VBA
> Project'
> command. My understanding of compiling is that it compresses the code
> files
> to remove various elements used when creating the program, and make the
> program ready for release. Is this correct?
>
> Do I need to compile my program before release, and if so, do I need to
> compile each .xls file individually?
>
> Thanks.

That sounds like a very complex project!
I would do a compile before every save, if there was any substantial code
change.
This will then pick any problems and avoid a save with these problems left
unfixed.
Also make sure that every module (normal module, class module and form
module) has Option Explicit at the top.

RBS


"dim" <(E-Mail Removed)> wrote in message
news:C8F576EF-EDF9-4050-B970-(E-Mail Removed)...
> Hi folks,
>
> My program consists of 197 .xls files in 5 sub-folders. 134 of these files
> contain programming and macros.
>
> The different files interact with each other in various ways, with
> different
> macros opening and closing other files at different times, and data being
> added to, removed from, or used by various files by macros when under the
> control of various other files.
>
> Anyway, In the Debug menu of the VBA Editor I see the 'Compile VBA
> Project'
> command. My understanding of compiling is that it compresses the code
> files
> to remove various elements used when creating the program, and make the
> program ready for release. Is this correct?
>
> Do I need to compile my program before release, and if so, do I need to
> compile each .xls file individually?
>
> Thanks.

Thanks folks,

That site pretty much explained it. I'll run the compile manually for each
of my files just in case.

Yeah, its the most complex Excel based program I've ever come across! lol
Unfortunately this is the final Exce build. For the next version I'm moving
over to C++.

Can you explain the Option Exlicit some more please, I've never used it?

> Can you explain the Option Exlicit some more please, I've never used it?

All explained nicely in the VBA help.
If you do in the VBE:
Tools, Options, Editor and tick Require variable declaration then Option
Explicit will always be automatically added for you when you add a new
module.

RBS


"dim" <(E-Mail Removed)> wrote in message
news:3438444F-FE4F-4636-A1D8-(E-Mail Removed)...
> Thanks folks,
>
> That site pretty much explained it. I'll run the compile manually for each
> of my files just in case.
>
> Yeah, its the most complex Excel based program I've ever come across! lol
> Unfortunately this is the final Exce build. For the next version I'm
> moving
> over to C++.
>
> Can you explain the Option Exlicit some more please, I've never used it?
>

You may want to read Dan Baarnes' white paper:
http://archive.baarns.com/excel/develop/vbaperfm.asp

Along with Robert Bruce's post:
http://groups.google.co.uk/group/mic...1b10a86ce16ae9

or

http://snipurl.com/2fh0n



dim wrote:
>
> Hi folks,
>
> My program consists of 197 .xls files in 5 sub-folders. 134 of these files
> contain programming and macros.
>
> The different files interact with each other in various ways, with different
> macros opening and closing other files at different times, and data being
> added to, removed from, or used by various files by macros when under the
> control of various other files.
>
> Anyway, In the Debug menu of the VBA Editor I see the 'Compile VBA Project'
> command. My understanding of compiling is that it compresses the code files
> to remove various elements used when creating the program, and make the
> program ready for release. Is this correct?
>
> Do I need to compile my program before release, and if so, do I need to
> compile each .xls file individually?
>
> Thanks.

--

Dave Peterson