Optimizing Access Applications
When Microsoft introduced 32-bit Access, a number of new performance concerns came part and parcel with the new features and functions. Microsoft continues to make a conscious effort to enhance the performance of the Access database engine, as well as compilation techniques and features such as the formerly undocumented Decompile command. The end result is that Microsoft has helped to ease your burden, but in no way has it completely taken that burden from you.
Tip: The published minimum RAM requirement for a computer to run Access on Windows XP (SP2 or later), Windows Server 2003 (or higher), or Windows Vista or Windows 7 is 256MB - with an emphasis on minimum. If you plan to do serious development with Access, you should have at least 512MB to 1GB of RAM or, preferably, 2GB or more.
With today's computers and memory prices, this amount of memory is a valuable investment. In fact, simply adding more memory will increase speed much more than changing your processor speed, because Access must use the hard drive as a virtual memory area if it doesn't have enough memory. Hard drives are slow, and big hard drives are even slower - regardless of the processor speed.
In this tutorial:
- Understanding Module Load on Demand
- Using the .accdb Database File Format
- Distributing .accde Files
- Understanding the Compiled State
- Application's code into a compiled state
- Distributing applications in a compiled or uncompiled state
- Creating a library reference for distributed applications
- Improving Absolute Speed
- Getting the most from your tables
- Getting the most from your queries
- Getting the most from your forms and reports
- Using bitmaps on forms and reports
- Getting the most from your modules
- Using control variables
- Eliminating dead code and unused variables
- Improving Perceived Speed
- Loading and keeping forms hidden
- Speeding up the progress meter display
- Working with Large Access Databases
- Recognizing that compiling and compacting
- Using the decompile option
- Detecting an uncompiled database and automatically recompiling