What the compilation can do for my program?

  • Thread starter Thread starter Mota
  • Start date Start date
M

Mota

Hi;
Do i have to necessarily compile my program before distributing it?What
benefit it has for my program?
Thank you.
 
Mota said:
Do i have to necessarily compile my program before distributing it?What
benefit it has for my program?
Click to expand...


First thing compiling does is check to make sure your code
can compile successfully. If it can't, your program will
not run.

The next thing compiling accomplishes is to compile the code
(DUH) so the users don't have to compile it when they run
your program. Other than being a time consuming process,
having the users compile it will also cause your program to
bloat to one degree or another. When you compile it prior
to distributing it, you can run Compact to reduce the size
of the distribution file.

OTOH, if your users may have different versions of some
libraries that your program references, then performing the
compilation on their machine will probably(?) resolve any
version conflicts that may exist. If possible, you should
do this, along with a Compact, as part of the instalation
process.
 
Mota said:
Hi;
Do i have to necessarily compile my program before distributing it?What
benefit it has for my program?
Thank you.
Click to expand...

Compiled code will execute marginally faster. Also, if you want to protect
your source code from others, compiling your app as an MDE has the benefit
of removing the source code and making it unviewable.
 
Does converting to MDE means and performs compiling ,also?Isnt it enough?
Thank you for your attention.
 
So,if i compile on my own machine,what happens to a probable version
conflict of refferences?Does my compilation have any profit on this matter?
Thank you.
 
Well, if you think verification that your code will compile
unimportant, I guess not. OTOH, compiling is really no big
deal and only takes a second or two. (Actually, I force a
compile after every code change.) Remember that a compile
error can prevent your program from running.

My release preparations start with a Compile and a Compact.
Then, I decompile the program and Compact again. After
saving a copy of the decompiled program, I then Compile
again.

If all that checks out, I then take the saved, decompiled
file to the client's site. Since each client enforces the
same system/software configuration on all of his machines (I
have not worked with one that allows willy nilly software
installations), I can then use the client's system to
compile a final version for that client. Note that this is
unnecessary if you are in a position to force all of your
clients to use exactly the same system that you use. I can
not even approach that sort of control over a disparate
client base, but I have heard of some developers that do.
 
Thats pretty right,but compiling increases the size of file,and since we
want to trade files thru Hyperterminal,file size is an important
matter.Thats all my question cause !
Thank you for all infos,and for your patience too.

Marshall Barton said:
Well, if you think verification that your code will compile
unimportant, I guess not. OTOH, compiling is really no big
deal and only takes a second or two. (Actually, I force a
compile after every code change.) Remember that a compile
error can prevent your program from running.

My release preparations start with a Compile and a Compact.
Then, I decompile the program and Compact again. After
saving a copy of the decompiled program, I then Compile
again.

If all that checks out, I then take the saved, decompiled
file to the client's site. Since each client enforces the
same system/software configuration on all of his machines (I
have not worked with one that allows willy nilly software
installations), I can then use the client's system to
compile a final version for that client. Note that this is
unnecessary if you are in a position to force all of your
clients to use exactly the same system that you use. I can
not even approach that sort of control over a disparate
client base, but I have heard of some developers that do.
--
Marsh
MVP [MS Access]

So,if i compile on my own machine,what happens to a probable version
conflict of refferences?Does my compilation have any profit on this matter?
Click to expand...
Click to expand...
 
Be sure you understand that your program will be compiled
whether you do it explicitly in the VBE or implicitly when
the code executes. This means that you will only reduce the
file size by using Compact, not by avoiding an explicit
compile.

If the recipients of your file are competent in Access, then
decompile and compact (without executing any code) to make
the absolute minimum file size for transmission. In this
scenario, it is best if the recipients explicitly compile
your program before they start using it.
--
Marsh
MVP [MS Access]

Thats pretty right,but compiling increases the size of file,and since we
want to trade files thru Hyperterminal,file size is an important
matter.Thats all my question cause !
Thank you for all infos,and for your patience too.

Well, if you think verification that your code will compile
unimportant, I guess not. OTOH, compiling is really no big
deal and only takes a second or two. (Actually, I force a
compile after every code change.) Remember that a compile
error can prevent your program from running.

My release preparations start with a Compile and a Compact.
Then, I decompile the program and Compact again. After
saving a copy of the decompiled program, I then Compile
again.

If all that checks out, I then take the saved, decompiled
file to the client's site. Since each client enforces the
same system/software configuration on all of his machines (I
have not worked with one that allows willy nilly software
installations), I can then use the client's system to
compile a final version for that client. Note that this is
unnecessary if you are in a position to force all of your
clients to use exactly the same system that you use. I can
not even approach that sort of control over a disparate
client base, but I have heard of some developers that do.
--
Marsh
MVP [MS Access]

So,if i compile on my own machine,what happens to a probable version
conflict of refferences?Does my compilation have any profit on this matter?


Mota wrote:
Do i have to necessarily compile my program before distributing it?What
benefit it has for my program?


"Marshall Barton" wrote
First thing compiling does is check to make sure your code
can compile successfully. If it can't, your program will
not run.

The next thing compiling accomplishes is to compile the code
(DUH) so the users don't have to compile it when they run
your program. Other than being a time consuming process,
having the users compile it will also cause your program to
bloat to one degree or another. When you compile it prior
to distributing it, you can run Compact to reduce the size
of the distribution file.

OTOH, if your users may have different versions of some
libraries that your program references, then performing the
compilation on their machine will probably(?) resolve any
version conflicts that may exist. If possible, you should
do this, along with a Compact, as part of the instalation
process.
Click to expand...
Click to expand...
Click to expand...
 
Seems thats the best way if compilation is recommended.Thank you for all
your comments.

Marshall Barton said:
Be sure you understand that your program will be compiled
whether you do it explicitly in the VBE or implicitly when
the code executes. This means that you will only reduce the
file size by using Compact, not by avoiding an explicit
compile.

If the recipients of your file are competent in Access, then
decompile and compact (without executing any code) to make
the absolute minimum file size for transmission. In this
scenario, it is best if the recipients explicitly compile
your program before they start using it.
--
Marsh
MVP [MS Access]

Thats pretty right,but compiling increases the size of file,and since we
want to trade files thru Hyperterminal,file size is an important
matter.Thats all my question cause !
Thank you for all infos,and for your patience too.

Well, if you think verification that your code will compile
unimportant, I guess not. OTOH, compiling is really no big
deal and only takes a second or two. (Actually, I force a
compile after every code change.) Remember that a compile
error can prevent your program from running.

My release preparations start with a Compile and a Compact.
Then, I decompile the program and Compact again. After
saving a copy of the decompiled program, I then Compile
again.

If all that checks out, I then take the saved, decompiled
file to the client's site. Since each client enforces the
same system/software configuration on all of his machines (I
have not worked with one that allows willy nilly software
installations), I can then use the client's system to
compile a final version for that client. Note that this is
unnecessary if you are in a position to force all of your
clients to use exactly the same system that you use. I can
not even approach that sort of control over a disparate
client base, but I have heard of some developers that do.
--
Marsh
MVP [MS Access]


Mota wrote:
So,if i compile on my own machine,what happens to a probable version
conflict of refferences?Does my compilation have any profit on this matter?


Mota wrote:
Do i have to necessarily compile my program before distributing it?What
benefit it has for my program?


"Marshall Barton" wrote
First thing compiling does is check to make sure your code
can compile successfully. If it can't, your program will
not run.

The next thing compiling accomplishes is to compile the code
(DUH) so the users don't have to compile it when they run
your program. Other than being a time consuming process,
having the users compile it will also cause your program to
bloat to one degree or another. When you compile it prior
to distributing it, you can run Compact to reduce the size
of the distribution file.

OTOH, if your users may have different versions of some
libraries that your program references, then performing the
compilation on their machine will probably(?) resolve any
version conflicts that may exist. If possible, you should
do this, along with a Compact, as part of the instalation
process.
Click to expand...
Click to expand...
Click to expand...
 
Back
Top