User Guide > Map Connectors > Source and Target Map Connectors > Visual dBASE 5.5
Was this helpful?
Visual dBASE 5.5
Visual dBASE 5.5 is a database application. With this connector, you can read and write Visual dBASE 5.5 files. If the data file references a memo field file, the memo file must exist for the connection to occur. The primary data file usually has a .DBF extension and the memo file usually has a .DBT extension. Visual dBASE 5.5 files are structured; for example, both the data and the file structure are stored inside the primary data file.
Connector-Specific Notes
• Field Names – Each field name must be unique. Field names must be all uppercase characters with an underscore between two words. Field names may contain up to 10 characters, but the first character must be a letter.
• Size of Fields – Character fields can be no longer than 254 characters. If a field is longer than 254 characters, it must be defined as a Memo field.
• Number of Fields – A maximum of 255 fields are allowed.
• Record Width – The maximum combined width of all fields in one record is 4000 bytes, excluding memo fields.
Connector Parts
Connector parts are the fields you configure to connect with a data source or target. The fields that are available depend on the connector you select.
For a list of all parts for source connectors, see Specifying Source Connector, Parts, and Properties.
For a list of all parts for target connectors, see Specifying Target Connector, Parts, and Properties.
Property Options
You can specify the following source (S) and target (T) properties:
Property
S/T
Description
IgnoreMemoErr
S/T
The following options determine how Visual dBASE memo files are handled:
• Never - this is the default. This option causes the integration platform to look for and include any memo file fields when the source data file is read.
• Errors - Selecting this option causes the integration platform to look for and include any memo file fields when a memo file is present. If present, the memo fields are included with the transformed data.
• If the memo file (.DBT) is not in the same directory as the data file (.DBF), the memo file is ignored. This means that the memo fields are not included with the transformed data.
• Always - Selecting this option causes the integration platform to ignore the memo file completely. This means that the memo fields are not included with the transformed data.
CodePage
S/T
This translation table determines which encoding to use for reading and writing data. The default is ANSI, the standard in the US.
Supported Data Types
The following data types are supported:
• Character – may contain alpha or numeric information and may have a field width of 1 to 254 bytes. Use a character field to store numbers that are not used in calculations, such as phone numbers, check numbers, account numbers and zip codes (number fields delete the leading zeros in some zip codes).
• Date – may contain only a date and the date is formatted as yyyymmdd, for a four-digit year, a two-digit month and a two-digit day. Example: The date January 1, 1999 would read 19990101.
• Float – may contain only positive or negative numbers and may have a field width of 1 to 20 bytes, including the decimal point, minus sign (-), or plus sign (+). Float fields are used to store small and largesmall and large numbers needed in scientific calculations, such as 9.1234e 12 or 9,123,400,000,000.
• Logical – may contain only one byte and is formatted to contain a t, f, T, or F, for true or false.
• Memo – may contain alpha or numeric information and may have a field width of 1 to 16,000 bytes.
• Numeric – may contain only positive or negative numbers and may have a field width of 1 to 20 bytes, including the decimal point, minus sign (-), or plus sign (+). A numeric field may contain decimal places up to 19, but the number of decimal places must be set at one byte less than the total width of the field. Numeric fields are used to store the exact value of a number with a fixed number of digits.
• Ole – embedded object
Last modified date: 12/03/2024