Word Document Properties

Part II: Learning the Ropes 
08_046500 ch03.qxp 12/5/06 5:34 PM Page 52

---

Every public 
Sub
that a user can access by using the Macro dialog box (as I
describe in Chapter 2) is a separate program. The 
SayHello
program that I
use in Chapter 2 is an example of a simple program that relies on a single
Sub
, but you can create programs of any complexity.
In Chapter 16, I demonstrate that a single program can cross project bound-
aries. All the examples in that chapter rely on the services of at least two
Microsoft Office products to perform a single task. Even though the program
is calling on the services of more than one Microsoft Office product, and it
resides in more than one location, it’s still a single program. Each example
contains a set of features required by the user to perform a given task. The
physical location and the use of external modules don’t affect this definition.
Understanding the VBA 
programming blocks
A VBA program consists of building blocks. In fact, because programming is
abstract, people tend to use physical examples to explain how things work.
You still need to know about the abstract elements of VBA programming, or
else you can’t write a program. This section explains the basic constructs of
VBA programming. In the upcoming “Taking the Lego Approach” section of
this chapter, I use a physical example as a means of describing these abstract
elements in detail. Consider only the four elements that I describe here:
Project:
The project acts as a container for the modules, class modules,
and forms for a particular file. In Word, you normally see a minimum of
three projects loaded into the Visual Basic Editor: the normal template,
the document template, and the document. Excel users normally see
just one project for the file that they have open.