Home
HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
LotusScript/COM/OLE Classes
LotusScript® Classes Coding Guidelines
The following topics cover some general guidelines for writing LotusScript® code using Domino® objects:
Using LotusScript® features in Domino®
All LotusScript® features work in Domino® exactly as specified in generic LotusScript, with the following exceptions and clarifications:
Using %Include and %If

HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
- What's new in HCL Domino Designer 12?
  The following features are new for developers in HCL Domino® Designer 12.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
- Domino® Query Language
  Domino® Query Language (DQL) is a facility running on a Domino server that provides a terse, shorthand syntax for finding documents. It supports a wide variety and complexity of search terms. It leverages existing design elements, avoiding the need to write detailed code to access them. DQL consolidates all methods in Domino for searching document contents.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
  - LotusScript® Classes Coding Guidelines
    The following topics cover some general guidelines for writing LotusScript® code using Domino® objects:
    - Using the Domino® classes
      Domino® Designer defines LotusScript® classes that allow you to access Domino structures on two levels:
    - Using LotusScript® features in Domino®
      All LotusScript® features work in Domino® exactly as specified in generic LotusScript, with the following exceptions and clarifications:
      - Using %Include and %If
      - Getting a returned array
        Arrays returned by Domino® properties and methods must be defined as Variant. You cannot define the return variable as a dynamic array. For example, you can do:
      - Closing a file
      - Using the Evaluate statement
      - Using an object
        This section shows you how to create an object, assign an object reference, and delete an object.
      - Using Bind, Command, Execute, InputBox, MessageBox, Print, SendKeys, Use, and UseLSX
      - Calling a function or subroutine
      - Using parentheses to pass by value
        You can pass an argument by value by enclosing it in parentheses. For example:
    - Accessing Domino® databases
    - Accessing views and folders
    - Accessing documents in LotusScript® classes
    - Accessing items in LotusScript® classes
    - Accessing rich text items in LotusScript® classes
    - Accessing sessions
    - Accessing supporting Domino® objects
    - Handling run-time errors
    - Accessing the Domino® Objects through COM
    - Using OLE
      The Notes® client is an OLE automation controller and server.
    - Using OLE custom controls
      You can embed OLE custom controls in Domino® Designer forms and write scripts for them just as you can for a native object. When a control is active (has focus), the menu is a combination of Domino Designer (File, Applet, and Window) and control items. The control menu items may include one for itself (for example, "Spreadsheet" for a spreadsheet control) and Help--the control help is substituted for Domino Designer help.
  - LotusScript® Classes A-Z
    This documentation lists each class, property, and method in the Domino® class library. Each class is followed by an alphabetical listing of the properties for that class and an alphabetical listing of the methods for that class. To find the property or method you want, turn to the class to which the property or method belongs.
  - LotusScript® Classes Tutorial
    Welcome to LotusScript® and Domino®. "LotusScript Classes Tutorial" consists of three lessons designed to introduce you to using the LotusScript language in Domino. Each lesson includes:
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Connectors
  Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.

Using %Include and %If

%Include

%Include directives must be placed in the (Declarations) event for an object. Do not place %Include directives in the event containing the execution code.

The %Include argument must be a string literal. Domino® does not permit a constant name or expression in this directive.

If you change the content of the file specified in an %Include directive, you must force recompilation of the script containing the %Include statement. To force recompilation, change some text in the (Options) or (Declarations) scripts containing the %Include directive, change it back, and save the object holding the script.

To use the LotusScript® constants, include LSCONST.LSS for non-error constants and LSERR.LSS for error constants:

%Include "lsconst.lss" 
%Include "lserr.lss"

To use the error constants for the Domino® objects, include LSXBEERR.LSS for the back-end objects and LSXUIERR.LSS for the front-end objects:

%Include "lsxbeerr.lss"
%Include "lsxuierr.lss"

%If

Domino® does not support the %If directive. (The Platform property of NotesSession provides the same information as the LotusScript® product constants WIN16, WIN32, and so on.)