First Question, is there any NATIVE connectors to PERVASIVE or BTRIEVE using the DDF format schema definition files/tables?
Does any one have success working with BTRIEVE or PERVASIVE files?
With the current ODBC driver accessing the PERVASIVE SQL tables, we are seeing in the TRANSFORMER that all the fields are NOT CORRECLTY matching the schema in the database.
For example the NUMBER fields are showing as CHAR(52) INSTEAD of as DOUBLE.
Dates are showing CHAR(6) instead of DATE.
Etc.
create table TableName (
AR_NAMEOVERLAY CHAR(13),
AR_ACCOUNTCODE CHAR(5),
AR_ACCOUNT# CHAR(52),
AR_ACCTTYPE CHAR(1),
AR_PRICE CHAR(52),
AR_QUANTITY CHAR(52),
AR_TONAGE CHAR(52),
AR_POUNDS CHAR(52),
AR_QTP CHAR(1),
AR_TOTAL CHAR(52),
AR_QTYDESC CHAR(30),
AR_INVOICE# CHAR(52),
AR_CONTRACT# CHAR(52),
AR_INVOICEDATE CHAR(6),
AR_CURRENCY CHAR(5),
AR_DOLLARRATE CHAR(52),
AR_LASTFINANCE CHAR(6),
AR_REMARK1 CHAR(1),
AR_REMARK2 CHAR(15),
AR_REMARK3 CHAR(60),
AR_FINACCT#DIV CHAR(1),
AR_FINACCT# CHAR(5),
AR_FINACCT#NUM CHAR(4),
AR_SHIPTRAN# CHAR(52),
AR_PAID CHAR(52),
AR_FLAG CHAR(1),
AR_TEMPAMOUNT CHAR(52),
AR_SALESTAX CHAR(52),
AR_MISC[1] CHAR(52),
AR_MISC[2] CHAR(52),
AR_MISC[3] CHAR(52),
AR_MISC[4] CHAR(52),
AR_MISC[5] CHAR(52),
AR_MISC[6] CHAR(52),
AR_MISC[7] CHAR(52),
AR_MISC[8] CHAR(52),
AR_MISC[9] CHAR(52),