"compiled state" for an access db

[Guest]

I just ran the performance analyzer on all objects in a db and one of the
suggestions it returned for optimization is that the db should be run in a
"compiled state."

I haven't heard this term before; any clues as to what it means?

Any resources on the web which explain this in detail would be helpful as
well, thanks.

 

[Allen Browne]

Open a code window.
Choose Compiled on the Debug menu.
If there are no errors, your database is now compiled.
You can verify that as the Compiled option on the menu is now greyed out. Or
you can do this in the Immediate Window (Ctrl+G):
? IsCompiled()

As for an explanation, Access keeps 2 copies of your code: the text version
that you see and edit, plus the compiled version that actually runs in the
processor. If the code is not compiled, Access must compile it, which takes
time, and so it executes more slowly.

Whenever you make a change to the code, it decompiles. michka did some
research on this several years back, and reported that although Access
reports the compiled state as yes or no, there are actually 11 different
states of compilation. You may be able to find that discussion in the
archives of microsoft.public.access or comp.databases.msaccess at:
http://groups.google.com/advanced_group_search?hl=en

 

[Guest]

Hi,

Thanks for the response.

The Compiled option on the menu is greyed out, however, when I enter ?
IsCompiled() in the Immediate Window, I get an error: "Compile error: Sub or
Function not defined"

 

[Guest]

Actually, ignore my last post.

I mis-typed compile in the Immediate Window.

Thanks,

Dave

 

[Guest]

hello
Dave F wrote in message