Article ID: 109382 - View products that this article applies to.
This article was previously published under Q109382
Novice: Requires knowledge of the user interface on single-user computers.
This article discusses whether the Visual Basic for Applications programming language (or the Access Basic programming language in version 2.0 or earlier) is a compiled language or an interpreted language.
Traditional compiled languages, such as C, compile human-readable source code into machine-readable, and much faster, object code. These object programs then need to be linked into an executable file to be used. Syntax errors are not generally located until the code is completely compiled. (Parsing compilers are an exception.)
Traditional interpreted languages, such as QBasic, use interpreters that read each line of code and translate it into computer instructions as you write it. An advantage of this method is that an interpreter can test your code as you write it. In some cases this line-by-line interpretation can be slow.
Visual Basic incorporates elements of both compiled and interpreted languages. Visual Basic does interpret each line of code as you write it, but Microsoft Access performs this interpretation in the background, and does not exhibit any performance degradation because of this interpretation.
In addition to this interpretation, Microsoft Access also compiles your code into a combination of compiled and interpreted code known as p-code, or pseudocode. This p-code runs much faster than interpreted code. The compilation takes place either when you first run the code, or when you click Compile All on the Run menu.
Microsoft Access 97 also provides another mechanism for keeping database applications compiled and secure. This feature is called Make MDE File. It removes the text representation of your Visual Basic for Applications code and stores just the binary compiled p-code.
If your database contains Visual Basic code, saving your database as an MDE file compiles all modules, removes all editable source code, and compacts the destination database. Your Visual Basic code continues to run, but it cannot be viewed or edited, and the size of your database is reduced due to the removal of the code.
Saving your database as an MDE file prevents the following actions:
Article ID: 109382 - Last Review: January 18, 2007 - Revision: 2.1
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Contact us for more help