Access Compliating

  • Thread starter Thread starter Warrio
  • Start date Start date
W

Warrio

Hello!

Regarding what is written in the Access's help about the "improvements in
compilation performance", is there a way to compile all modules when the
user lunches the database?

Or is enough to do it, once the programmer have finished the changes to the
db, to go into vba and click on the menu "Debug, Compile Access9db"?

Thanks for any suggestion!
 
Warrio,

Once should be enough, if no change is made to the source code, there's
no need for recompiling. Just consider this: the most common form to
distribute apps to users is .mde, which has no source code, just
compiled code.

HTH,
Nikos
 
Great thanks Nikos for the quick response
is there any information that can tell me more about the file .mde?
I want to how access works and it decides on which modules to compile first

Thanks again!
 
Warrio said:
Great thanks Nikos for the quick response
is there any information that can tell me more about the file .mde?
Click to expand...
Look up "MDE files" in Access help, it will tell you quite a lot.
I want to how access works and it decides on which modules to compile first
Click to expand...
You got me there, no idea! Suggest you make a new post in the
modulescoding newsgroup.
 
During development, you compile to have syntax and code errors discovered.
Thus, during development, you should compile often. in fact, I compile every
time i make a code change.

Of course, when you done making changes to your application, then you want
to make a mde file. A mde file is already compiled, and thus no further
compiling is needed. This also means that to make a mde, no compile errors
can exist (so, a mde is a nice "final" check before you distribute).

In addition, a mde is already compiled, and users can't change it.
 
Warrio,

I don't know how Access decides what order to compile modules in, but I
don't think it is important. When you compile, it compiles all the code in
the database. An mde is the same as an mdb functionally; however, as Nikos
stated, you cannot see any code. You cannot open any object in design view.
It is designed to allow users to execute code but prevent them from making
any changes. An mde will be smaller in size than the mdb it was created
from. It is not difficult to create an mde, from the main tool bar select
Tools->Database Utilities->Make MDE File.
 
Thanks for the help!!!
so, the mdb is a sort of an .exe file?
but how come that this function (Make an MDB File) is disabled with the
access that I'm using (Access2002)??

Thanks again!
 
I need to convert it to 2002 file format first!


Warrio said:
Thanks for the help!!!
so, the mdb is a sort of an .exe file?
but how come that this function (Make an MDB File) is disabled with the
access that I'm using (Access2002)??

Thanks again!
Click to expand...
 
Back
Top