|
This section describes the objects on Function Executor graphical user interface (GUI).
Click on an area of the image to learn more.
A main window displays for every open file. Click on an area of the image to learn more.
The Login and Logout dialog boxes allows you to perform the Btrieve login and logout operations, respectively, for the database engine. Click on an area of the image to learn about this dialog box.
|
GUI Object
|
Description
|
|---|---|
|
Server
|
Specifies the server where the database resides that you wish to login to or logout from.
|
|
Database
|
Specifies the database on the server to which you want to authenticate.
|
|
User Name
|
The user name you want to authenticate against the database.
|
|
Password
|
The password for the user name.
|
|
Client ID
|
If you want this login or logout to apply to a specific client ID, click Use and specify the range. Otherwise, leave as is.
See Client ID in Btrieve API Guide.
|
|
URI String
|
As you enter information in the forms, the URI resulting from your selections is shown in this area.
|
This dialog box allows you to open a file. Click on an area of the image to learn about this dialog box.
|
GUI Object
|
Description
|
Related Information
|
|---|---|---|
|
Filename
|
Specifies the location and name of the file that you want to open.
|
|
|
Owner name
|
Specifies a password to associate with the Btrieve file. If specified, the owner name is required to gain access to the Btrieve file. Owner name has no relation to any system user name. You can think of an owner name as a simple file password.
|
See also the chapter Pervasive PSQL Security in Advanced Operations Guide.
|
|
Mode
|
Specifies the state of the file when it is opened. Based on the state, the database engine knows certain conditions that apply to the opened file. For example, a condition could be that the file can be read but not updated (read-only).
|
See Open Modes in Btrieve API Guide for an explanation of the modes. That guide is part of the Pervasive PSQL Software Development Kit (SDK).
|
|
Client ID
|
If you want this login to apply to a specific client ID, click Use and specify the range. Otherwise, leave as-is.
|
|
|
Sharing
|
The database engine ignores the "Sharing" options. The "Sharing" options applied only to a legacy version of the engine, Btrieve 6.15.
|
This dialog box allows you to create a Btrieve file. Click on an area of the image to learn about this dialog box.
|
GUI Object
|
Description
|
Related Information
|
|---|---|---|
|
Filename
|
Specifies the location and name of the file that you want to create.
|
|
|
Owner name
|
Specifies a password to associate with the Btrieve file. If specified, the owner name is required to gain access to the Btrieve file. Owner name has no relation to any system user name. You can think of an owner name as a simple file password.
|
See also the chapter Pervasive PSQL Security in Advanced Operations Guide.
|
|
Mode
|
Specifies the state of the file when it is opened. Based on the state, the database engine knows certain conditions that apply to the opened file. For example, a condition could be that the file can be read but not updated (read-only).
|
See Open Modes in Btrieve API Guide for an explanation of the modes. That guide is part of the Pervasive PSQL Software Development Kit (SDK).
|
|
Client ID
|
If you want this login to apply to a specific client ID, click Use and specify the range. Otherwise, leave as-is.
|
|
|
Sharing
|
The database engine ignores the "Sharing" options. The "Sharing" options apply only to a legacy version of the database engine, Btrieve 6.15.
|
This dialog box allows you to specify additional characteristics for the file being created. Click on an area of the image to learn about this dialog box.
This dialog box allows you to control transactions during your Function Executor session. Click on an area of the image to learn about this dialog box.
|
GUI Object
|
Description
|
Related Information
|
|---|---|---|
|
Main application window
|
Main features of the program.
|
|
|
Transaction type
|
Specifies whether you want an exclusive or concurrent transaction.
|
|
|
Lock information
|
Specifies the type of locking you want in the transaction.
|
|
|
Start transaction button
|
Starts a transaction.
|
|
|
Commit transaction button
|
Commits the active transaction.
|
|
|
Abort transaction button
|
Cancels the active transaction and rolls back any changes made.
|
|
|
File area
|
This area contains one or more open files.
|
See Main Window
|
|
Transaction indicator
|
Indicates whether you are currently in a transaction. If you are in a transaction, this display will show either Concurrent or Exclusive.
|
This dialog box allows you to see the statistics for a Btrieve file. Click on an area of the image to learn about this dialog box.
|
GUI Object
|
Description
|
|---|---|
|
File information
|
Displays statistical information about the file.
|
|
Flags
|
Allows you to view the flags set for this file. Any flag that is set will have a check mark next to its listing in the dialog box.
|
|
Keys
|
Allows you to view the keys defined in this file.
|
|
Key legend
|
Describes the single letter values that indicate Key attributes for the file.
See also Key Attributes in Pervasive PSQL Programmer's Guide.
|
|
Print button
|
Allows you to print the file statistics. Set up the printer using the File menu.
|
|
Save button
|
Allows you to save the current file statistics to a description file, which you can later use to make a new file with the same characteristics.
|
|
Exclamation point (create new file)
|
Allows you to create a new file based on these file statistics.
|
This dialog box allows you to see all the operations you have performed. Click on an area of the image to learn about this dialog box.
|
GUI Object
|
Description
|
Related Information
|
|---|---|---|
|
File menu
|
Allows you to perform the following operations:
|
|
|
Settings menu
|
Allows you to specify the visual attributes of the History window.
|
|
|
Execute command
|
Loads the History Playback window
|
|
|
List of operations
|
Lists operations that you have recently performed. Each operation is logged with the following information:
|
|
|
Logging
|
Toggles the inclusion of future operations in the history list.
|
|
|
OpCode Names
|
Toggles the display in the Operation column between operation code names (such as B_OPEN) and operation code numbers (such as 0 for B_OPEN)
|
|
Chapter contents
Prev topic: Function Executor Concepts
|