User Guide : Map Connectors : Source and Target Map Connectors : Btrieve 10
 
Share this page             
Btrieve 10
Btrieve is a transactional database interface. To use the Btrieve 10 connector, you must install Btrieve on both the system where the integration platform is used and on the system where transformations are run.
The following table shows read-write capabilities for the Btrieve connectors and Btrieve files.
Connector
v11
Btrieve v9.5 file
RW
Btrieve v9 file
RW
Btrieve v8 file
RW
Btrieve v7 file
RW
Btrieve v6 file
RW
Btrieve v5 file
R
Btrieve v4.11 file
R
Btrieve Data Dictionary Files
Btrieve is a transactional database interface. To use any of the Btrieve connectors, you must install the Btrieve version on both the system where Map Editor is used and on the system where transformations are run.
Btrieve can use data dictionary files (DDFs). If your Btrieve files have no DDFs, use Pervasive DDF Builder to create them before connecting to Btrieve source or target data.
Connector-Specific Notes
Single record type files
In general, Btrieve files must be fixed, sequential files. For example, each record must be the same number of bytes and each field must occupy the same set of bytes in each record. For example, if record 1 is 236 bytes long, every record must be 236 bytes long. If the first field in record 1 occupies 4 bytes and is a 32-bit binary data type, then the first field in every record must do the same.
The integration platform does not support Btrieve files with records of variable length except when the variable records are at the end of the file after the fixed records. If so, the integration platform reads only the fixed records.
After writing to a Btrieve target, transformations do not update the Btrieve DDF index file. You must do this in Btrieve.
Multirecord type files
It is possible to work with variable-length multirecord files, with and without a record separator, using certain guidelines. For more information, search for "multiple record" in the documentation.
Truncation Error Trapping
This connector does not support truncation error trapping. If the target field size is too small for the data written to it, the offending record may be skipped or incomplete data may be written to the target. The transformation does not stop due to a truncation error, as do connectors that have truncation support.
Property Options
These are properties that you may need to specify for your source or target data.
Property Name
S/T
Description
Page Size
ST
This option sets the page size for Btrieve data. The default value is 4096. To change the page size, enter a new value in increments of 512. See the Btrieve documentation for your correct page size.
CodePage
ST
This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US.
Data Types
The following data types are supported for a Btrieve data file:
32-bit IEEE floating-point
64-bit IEEE floating-point
Autoinc (2 bytes)
Autoinc (4 bytes)
Bfloat (4 bytes)
Bfloat (8 bytes)
Bit
BLOB
Character (default)
CLOB
Comp
Comp-1
Comp-3
Comp-5
Comp-X
Currency
Date
Decimal
Float (4 bytes)
Float (8 bytes)
GUID (Btrieve 10 only)
Integer (1 byte)
Integer (2 bytes)
Integer (4 bytes)
Integer (8 bytes)
Logical
Logical (2 bytes)
Lstring
Lvar
Magic PC Date
Magic PC Extended
Magic PC Number
Magic PC Real
Magic PC Time
Microsoft BASIC double
Microsoft BASIC float
Money
Note
Numeric
NumericSA
NumericSTS
Packed decimal
Sales Ally time-2
Sales Ally date
Sales Ally time-1
Time
Timestamp
Unsigned (1 byte)
Unsigned (2 bytes)
Unsigned (4 bytes)
Unsigned (8 bytes)
Wstring
Wzstring
Zoned decimal
Zstring