Microsoft Access version 2.0 has code modules that are scoped to particular forms or reports. We call this Code Behind Forms, or CBF. There are several advantages to placing CBF for application development in general, for Wizard development in particular. First, it reduces the likelihood of variable name conflicts. Second, it can improve overall performance. This is because all global Access Basic code is loaded into memory when Microsoft Access launches. On memory-constrained machines, this forces more swapping and hurts performance. CBF, on the other hand, isn't loaded into memory until the form is loaded and is discarded when the form is closed. Thus, users don't pay the performance penalty for the memory footprint of code that they aren't using. The downside to this strategy is that the Wizard takes slightly longer to load. This section gives you an overview of how CBF can be used in Wizard development.