|
|
|
|
|
|
|
|
|
|
- Overview
- Instances of an executable file
- Modes for using the library
Instances and library of an executable file
The operating mode of an executable allows you to define whether the executable can be used by one or more users. The main library of an application groups all the elements handled by this application (windows, reports, classes, set of procedures, queries, data files) and their dependencies (images used in the windows for example). For more details, see the help about the libraries. Note: To create the executable file, use one of the following methods: - On the "Project" tab, in the "Generation" group, click "Generate".
- Expand
 in the quick access buttons and select "Generate 32-bit Windows executable (.exe)" or "Generate 64-bit Windows executable (.exe)".
The executable creation wizard allows you to define the operating mode of the executable and the modes for using the library. Instances of an executable file The executable file can use one of the following modes: - multiple instances. A program can be run multiple times on the same computer. This means multiple instances of the program will be open simultaneously.
- single instance. A single-instance program can be started once only from the same computer. If the user tries to start another instance of the program, the current instance will be automatically enabled.
Modes for using the library The use modes of the library are as follows: - including the main library in the executable. This option is used to create (or modify) the main library of the current application and to include this library in the executable program.
To update the main library, the executable program must be recreated. - external use of the main library. This option is used to create (or modify) the main library of the current application and to associate this library with the executable program.
To update the main library, this library must be recreated. - use no library. No library will be associated with or included in the executable program. This option is kept for backward compatibility. For more details, see Creating an executable without library.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|