Basic product usage information and programming language reference information.
Welcome to the LotusScript® Language section of Domino® Designer Help.
The flow of execution of a script generally follows the sequence of statements in the script. This chapter describes the behavior of particular statements that alter the flow of execution.
Welcome to the Application Design section of Domino® Designer Help.
The templates described in the following table are available with Domino® Designer and are specifically intended for use by application developers.
Domino® Designer Release 6 and later supports the messaging application program interface (MAPI), which allows mail integration between Domino and a MAPI-compliant messaging application, such as Microsoft™ Outlook, Microsoft Office applications, or user-written C++ programs.
Developers creating applications specifically for the Web, or for the dual purpose of serving Notes® and Web clients, should review the following tables for features that are not supported on the Web.
You have a variety of options for programming a Web site. You can directly manipulate objects such as documents or views in an application using Domino® URL commands. Adding Domino URL commands as HTML in forms gives users shortcuts for navigating databases and performing other tasks quickly.
Welcome to the Application Management section of Domino® Designer Help.
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.
Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
This section documents the formula language.
This chapter introduces LotusScript® and describes, in general terms, how to use the script editor to write and modify scripts, how to compile scripts, and how to use the debugger to locate problems in the logic of your applications.
This chapter describes the rules for writing the basic elements of a script in the LotusScript® language.
This chapter provides information about LotusScript® constants and variables and the data types of the values that they can represent.
This chapter describes the set of LotusScript® operators, how they may be combined with operands to form expressions, and how those expressions are evaluated.
This chapter describes file handling in the LotusScript® language.
This chapter describes error processing in the LotusScript® language.
This chapter describes two kinds of custom data structures that you can define in LotusScript®. Each can hold data of different types in a single data structure.
The flow control statements that alter the flow of execution fall into several functional groups:
Comments are not executed. These include any source text preceded on a line by the comment marker apostrophe ('), the text in a Rem statement, and the text enclosed between the compiler directives %Rem and %End Rem. The LotusScript® compiler reads and discards these.
Declarations include the Declare statement for forward references, the Declare statement for external C calls, the Const statement, and the Dim statement. With one exception, declarations do not produce executable code. The result of a declaration is information about a procedure, a variable, or a constant; for example, its type, dimensions, or value. This governs the behavior of the script that uses the declared item; but the declaration itself is not executed when the script runs.
A few other statements also produce no executable code. These include Option Base, Option Compare, Option Declare, and Option Public; the Type statement; and the Deftype statements.
The flow of execution may also be changed at run time by the occurrence of an error. Either execution ends, or an On Error statement in the script specifies how to respond to the error, in one of these ways:
Statement labels can appear only within procedures. A statement at module level in a script -- not contained within a procedure -- cannot be labeled. Since any given label is known only within the procedure where it is defined, a branching statement that may transfer control to a labeled statement can appear only within the same procedure as the labeled statement. The statements that may transfer control to a labeled statement are GoTo, GoSub, On...GoTo, On...GoSub, If...GoTo...Else, and Resume. If an error occurs that is governed by an On Error...GoTo label statement, the On Error statement and the labeled statement must be in the same procedure.
This chapter describes how to use multiple threads and synchronization to manage HTTP agents with Domino®.
This chapter discusses the role that LotusScript® plays with IBM® products, your operating environment, other programs, and interactive user applications.
This chapter describes the use of statements, built-in functions, subs, data types, and directives in the LotusScript® language.
This appendix describes LotusScript® language limits of several kinds: for example, the legal ranges in data representation, the limits on numerical specifications within statements, and the maximum number of different kinds of elements that can be defined in a script.
The LotusScript® language and functionality on the UNIX™ platform, the Macintosh platform, and the OS/400® platform differ in various ways from the language and functionality described in the rest of this language reference. This appendix describes the differences.
This appendix provides an overview of REXX integration in the LotusScript® language.
This appendix lists the LotusScript® aliases and their equivalent text.
This chapter describes the compile-time error messages in the LotusScript® language.
This chapter describes the run-time error messages in the LotusScript® language.
This section documents the Java/CORBA classes.
Lotus® Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.
Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.