Home
HCL Domino Designer Basic User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
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.
Accessing external databases through LS:DO
Developers are advised not to use LS:DO. Developers should use the Connector LSX for (LCLSX) when accessing external data sources.
ODBCQuery (LotusScript)
Represents the ODBC data access features for defining an SQL statement.
UseRowID (ODBCQuery - LotusScript)
Specifies whether data in the back-end database is accessed by row ID.

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 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
- 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.
  - Connectors and Connectivity Guide
  - LSX for Connectors
    LotusScript® Extensions for Connectors (LC LSX) enhances the power of Notes® by extending its scripting to data outside of Notes through the use of Connectors. The programming model is independent of the individual connector. This eliminates the need to learn each individual system, while at the same time allowing experienced users to access the individual features of a specific system.
  - Accessing external databases through LS:DO
    Developers are advised not to use LS:DO. Developers should use the Connector LSX for (LCLSX) when accessing external data sources.
    - Setting up LS:DO
      Setting up LS:DO requires several steps, in which you install any needed software, register your data sources, and then create your script. Review the following sections as you set up LS:DO for your application:
    - Using LS:DO
      Once you have set up LS:DO and your script, you are ready to access your external databases. With LS:DO, you can:
    - Tips and techniques
      This section presents specialized topics concerned with enhancing your LS:DO application:
    - ODBCConnection (LotusScript)
      Represents the ODBC Data Access features for connecting to a data source.
    - ODBCQuery (LotusScript)
      Represents the ODBC data access features for defining an SQL statement.
      - Examples: ODBCQuery class
        The following agent creates a query that retrieves all the rows in the STUDENTS table of the ATDB data source.
      - Connection (ODBCQuery - LotusScript)
        Write-only. Relates a connection object with a query.
      - QueryExecuteTimeOut (ODBCQuery - LotusScript)
        Read-write. Specifies a time-out value in seconds for query execution.
      - SQL (ODBCQuery - LotusScript)
        Read-write. Any SQL statement.
      - UseRowID (ODBCQuery - LotusScript)
        Specifies whether data in the back-end database is accessed by row ID.
        Examples: UseRowID property
        This example shows you how to enable "select by row ID" mode and then access rows by their IDs, for example, in an Informix database. Remember to place the qry.UseRowID = True statement before the qry.SQL = [SQL statement] in your script, as shown below.
      - GetError (ODBCQuery - LotusScript)
        Returns the latest error code for an ODBC object.
      - GetErrorMessage (ODBCQuery - LotusScript)
        Returns the short error message text associated with an error code.
      - GetExtendedErrorMessage (ODBCQuery - LotusScript)
        Returns the long, descriptive error message text associated with an error code.
    - ODBCResultSet (LotusScript)
      Represents the ODBC data access features for performing operations on a result set.
- 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.

UseRowID (ODBCQuery - LotusScript)

Specifies whether data in the back-end database is accessed by row ID.

Defined in

ODBCQuery

Syntax

To get: flag% = odbcQuery . UseRowID

To set: odbcQuery . UseRowID = flag%

Data type

Boolean

Legal values

True indicates that "Select by row ID mode" is set.
False indicates that "Select by row ID mode" is not set; default.

Usage

UseRowID defaults to False; most databases do not support access by row ID. Set UseRowID to True when you want to use "Select by Row ID mode" (the back-end database must support this type of access). You must set this type of access before using the SQL property to define your SQL statement.

Example