Using Bind, Command, Execute, InputBox, MessageBox, Print, SendKeys, Use, and UseLSX


Domino® Designer implicitly binds its supported objects. Do not use Set...Bind to associate a Domino® object with a variable.


The Command function always returns an empty string.


If you modify a global variable in an Execute statement, the variable must be defined in the (Declarations) event for (Global), not the (Declarations) event for the object containing the script.

InputBox and MessageBox

The Inputbox and MessageBox functions write to the following:

  • A dialog box when executing on a Domino® client. The user clicks OK, Cancel, Abort, Retry, Yes, or No to continue.
  • log.nsf when executing on a Domino® server.


The Print statement writes to the following:

  • The status bar when executing on a Domino® client in non-debug mode.
  • The status bar and output window when executing on a Domino® client in debug mode.
  • NOTES.LOG when executing on a Domino® server.


The LotusScript® SendKeys statement is not currently supported in Domino® Designer.

Use and UseLSX

The Use statement is supported in Domino® Designer. This statement loads an LSS file containing public definitions, and also loads a script library.

The UseLSX statement is supported. This statement loads a shared library of class definitions. Once the LSX file has been loaded, you can view its classes in the Notes® class browser. These class definitions are then available to scripts.

The Domino® platform has a registry of LSX. If the file-specification string in the UseLSX statement begins with an asterisk (*), then Domino® Designer looks in the registry for the name consisting of the rest of the string. The registry entry for that name specifies the file location in the platform file system.