LotusScript for Visual Basic Programmers - IBM Redbooks

Error Checking
There are two types of error checking performed in the script editor:
1. Each time you move the cursor to a different line, by pressing ENTER,
using a cursor movement key, or clicking with the mouse, Notes will
check the syntax of that line in isolation. This kind of syntax check picks
up errors such as unmatched parentheses and incomplete expressions.
Notes does not force you to fix these errors right away. You can
continue entering code. However, Notes will not allow you to save the
form until the error is corrected.
2. Whenever you save the form, Notes will compile the LotusScript code,
and may uncover other errors, such as a Select Case statement with no
matching End Select statement, and invocations of methods which the
object does not support. When such a compile error is found, Notes will
display the following message box:
Testing the Form
If you click Yes, the form is not saved and you can go and edit the code
to correct the error. If you click No, the form is not saved and any
changes you made since the last successful save are lost.
Choosing Design → Test Form will cause the form to be saved, and a new
document created based on the form. You can then run this new document
through its paces to check on how the code you wrote for the form is
performing. When you complete your testing, press ESC (Notes will ask you
if you want to save the document) to take you back to the form design IDE.
Debugging LotusScript
It is possible that all of your LotusScript statements are syntactically correct,
and that your program compiles without error, and yet it will not run
correctly. Consider this very simple code fragment:
If A + B Then C = 0
What the programmer meant to type is
If A = B Then C = 0
but in haste, the SHIFT key was not released in typing the equals sign, and
the plus sign was typed instead. Both statements are syntactically correct,
40 LotusScript for Visual Basic Programmers