Word Document Properties

myDebug = 1
. Click OK and then
run the program again. The program displays a message box that reads 
In
Debug Mode
.
Locking your code
At some point, you might decide that you want to lock away your code 
forever so that no one can modify it. The Protection tab of the Project
Properties dialog box, shown in Figure 3-8, helps you accomplish this task.
Simply select the Lock Project for Viewing check box, and then supply the
same password in both the Password and Confirm Password fields. Click OK
to complete the process.
Locking your project might seem like a good idea, but you should carefully
consider whether to do so, for a number of reasons. The most important
reason is that you can’t unlock the project without the password. If you
forget the password, the project might remain locked forever. The second
reason is that locking your project doesn’t prevent someone from viewing
your code. The only thing that locking the project does is to prevent some-
one from modifying the code. Consequently, when you need to hide the code
for some reason, VBA isn’t the best tool for the job. (If hiding your code is
essential, you need a native code compiler, such as Visual C++, or a product,
such as Visual Studio Tools for Office [VSTO], that can integrate managed
code solutions with Office products.)
Figure 3-8:
Locking
your code
can keep it
safe from
prying eyes.
64
Part II: Learning the Ropes 
08_046500 ch03.qxp 12/5/06 5:34 PM Page 64

---

Defining compiler options
When you first start VBA, it makes certain assumptions about how you want
to write code. These assumptions might not be accurate, so Microsoft pro-
vides a way for you to tell VBA to do something else. The compiler options
listed in Table 3-1 help you define how VBA works with your code. (A 
compiler
reads your code and translates the words into instructions that Windows can
understand.) You can add these options at the very beginning of a module,
class module, or form, before any other code appears.