This section contains extra information relating to the deployment of the Easysoft ODBC-Quickbooks Desktop Driver.
The Easysoft ODBC-Quickbooks Desktop Driver complies with the ODBC 3.51 specification.
The Easysoft ODBC-Quickbooks Desktop Driver is Level 2 compliant.
All ODBC 3.51 calls are supported.
If the Easysoft ODBC-Quickbooks Desktop Driver implements a RQUseCachedID column for a table, a cache enabling requests to be batched together is available for that table.
The cache is committed or rolled back when an end transaction is sent. If your application allows you to turn autocommit off, you can execute several INSERTS or UPDATEs in one batch. For example:
INSERT INTO BillItemLine ("VendorRef_listID", "RefNumber", "ItemGroupLine_ItemGroupRef_ListID" ) values ('8000007A-1356973501', 666, '80000089-1349127814' )
INSERT INTO BillItemLine ("ItemGroupLine_ItemGroupRef_ListID", "RQUSeCachedID" ) values ('80000088-1349127627', 1 )
INSERT INTO BillItemLine ("ItemLine_ItemRef_ListID", "RQUSeCachedID" ) values ('8000001A-1356973474', 1 )
Each time a new record is inserted or a record is updated, the relevant ID (ListID or TxnID) is added to the cache along with the latest edit sequence.
When autocommit is on, RQUseCachedID or TxnID/ListID can be to insert or update records, however each insert or update is a seperate transaction.
The ODBC calls an application makes can be traced:
An application can turn tracing on in the Driver Manager by using the ODBC API SQLSetConnectAttr (...,SQL_ATTR_TRACE,...).
The trace file name may also be specified with the SQLSetConnectAttr attribute SQL_ATTR_TRACEFILE.
Driver manager trace files show all the ODBC calls applications make, their arguments and return values. Easysoft ODBC-Quickbooks Desktop Driver driver tracing is specific to the Easysoft driver and is of most use when making a support call.