PreviousBtrieve API Guide (v9 SP2 (9.5) revision 1) Next

Summary of Btrieve API Operations

Chapter contents

The Btrieve API provides over 40 operations that you can call from your application program. The following tables summarize these operations. Refer to Chapter 2, Btrieve API Operations, for complete descriptions of the Btrieve API operations. Refer to Appendix A, Quick Reference of Btrieve Operations, for a summary of Btrieve API operations ordered by operation code.

Session-Specific Operations

The following operations allow you to set or retrieve the current directory, shut down a workstation transactional interface, retrieve the transactional interface version number, terminate a client connection with the server transactional interface, and begin, end, or abort a transaction. In applications that handle multiple clients, these operations are specific to the calling client.

Table 1-3 Session-Specific Operations 
Operation
Code
Description
Set Directory
  17
Changes the current directory.
Get Directory
  18
Returns the current directory.
Stop
  25
Terminates the workstation transactional interface (not available for server-based transactional interface).
Version
  26
Returns the version number of the transactional interface.
Reset
  28
Releases all resources held by a client.
Begin Transaction
  19 1019
Marks the beginning of a set of logically related operations. Operation 19 begins an exclusive transaction. Operation 1019 begins a concurrent transaction.
End Transaction
  20
Marks the end of a set of logically related operations.
Abort Transaction
  21
Removes operations performed during an incomplete transaction.

File-Specific Operations

The following operations deal with a specific file, and therefore use the position block parameter to identify the file on which to operate. The file-specific operations are of three types:

Unsupported Operations

When looking at transactional interface traces or SDK header files, you may see operations that are not listed in the reference for Btrieve API operations. These are for the internal use of Pervasive PSQL and you should not use them in your applications. The following operations are not supported.

Table 1-7 Unsupported Operations 
Operation
Code
Description
B_MISC_DATA
  41
Reserved for use by transactional interface
B_EXTEND
16
Reserved for use by SQL engine
Begin Transaction (nested) via Btrieve
2019
Reserved for use by transactional interface


Chapter contents
Book contents

Prev topic: Btrieve API Function Parameters
Next topic: Sequence of Events in Performing a Btrieve API Operation