Home
HCL Domino Designer 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:
Accessing the Domino® Objects through COM
Language differences between LotusScript® and Visual Basic
Note the following language differences between LotusScript® and Visual Basic:

HCL Domino Designer User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
- What's new in Domino Designer 14.5?
  The following features are new for developers in HCL Domino® Designer 14.5.
- What's new in Nomad Designer?
  HCL Nomad for web browsers v1.0.10 introduces the capability to design Notes databases. For more information, see HCL Nomad for web browsers User Documentation, Nomad web Designer.
- 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:
    - 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
      - Examples: Accessing the Domino® Objects through COM
      - Requirements
        The COM interface is available on a computer containing any of the following:
      - Creating a session object
        To access the Domino® Objects, create an object based on the registered Lotus®.NotesSession class.
      - Initializing a session
        You must explicitly initialize a COM session with one of the following NotesSession methods. These methods do not apply to LotusScript® applications.
      - General exceptions to LotusScript® specifications
        The following are the general differences between accessing Domino® Objects through either LotusScript® or COM:
      - Language differences between LotusScript® and Visual Basic
        Note the following language differences between LotusScript® and Visual Basic:
      - Specific exceptions to LotusScript® specifications
        The following are specific differences between accessing Domino® Objects through either LotusScript® or COM.
      - COM-only properties and methods
        Following are the specifications for the COM-only properties and methods:
      - Constants
        The table that follows specifies the values of the non-error constants used by the Domino® classes. You can also see the constant values by examining domobj.tlb in the Notes® or Domino program directory with a product such as Visual InterDev (VID).
    - 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.

Language differences between LotusScript® and Visual Basic

Note the following language differences between LotusScript® and Visual Basic:

LotusScript® uses ForAll ... End ForAll. Visual Basic uses For Each ... Next.
Visual Basic does not support the compiler directives %Rem, %End Rem, %If, %Elseif, %Else, %End If, and %Include.
Visual Basic does not support the vertical bar | and braces {} for delimiting strings.
Visual Basic does not support &B for binary literals. It does support &H and &O for hexadecimal and octal literals.
LotusScript® uses Format to format dates. Visual Basic uses FormatDateTime.
LotusScript® does not support CDec.
Visual Basic does not support Today.
LotusScript® does not support the Err intrinsic object. Visual Basic does not support On Error with an error number as a parameter.