Icon Application Compatibility

Supported Applications
The DBISAM ODBC driver is an ODBC level 3 driver. We have tested the driver successfully with Microsoft Data Access Components (MDAC) version 2.7 or higher and the following applications:

ApplicationVersions and Notes
Crystal Reports8.5 and later

Version 9 requires a patch in order to run correctly. Please see the technical bulletin regarding this issue for more information:

Problems with ODBC Driver and Crystal Reports 9
Microsoft Office2000 and later

Microsoft Access has problems with using an auto-increment field as part of the primary index since the Jet engine cannot "discover" the keys properly when they are not populated explicitly by the client application.
Microsoft Visio2000 and later
Borland Database Engine (BDE)5.01 and later

With the BDE there are problems with using an auto-increment field as part of the primary index since the BDE cannot "discover" the keys properly when they are not populated explicitly by the client application.
ODBCExpress5.06 and 7
Microsoft IIS ASP5 and later

It is recommended that you only use the ODBC functionality in ASP and not the ADO->OLEDB->ODBC bridge driver through the ADO functionality. The bridge driver does not function correctly in most cases.
Microsoft Visual Basic6 and later

It is recommended that you only use the ODBC functionality in VB 6 and not the ADO->OLEDB->ODBC bridge driver through the ADO functionality. The bridge driver does not function correctly in most cases.
Microsoft Visual Studio .NET2002 and later

It is recommended that you only use the ODBC.NET data provider with any .NET application (VB.NET, ASP.NET, C#, Delphi.NET, Chrome). Also, since the ODBC.NET data provider is accessing and using unmanaged resources and handles in the ODBC driver during operation, you should always call the Dispose method for any ODBCConnection, ODBCCommand, ODBCCommandBuilder, or ODBCDataAdapter objects when you are done using them (deterministic destruction). Failure to do so can cause major failures in the driver due to the resources and handles being freed up re-entrantly when the .NET garbage collector thread finalizes these objects.

Missing Features
There are still a few things missing from the driver, but they should not affect most environments. These missing items are:

Support for bulk operations (specifically the SQLBulkOperations call)
Support for a few ODBC extended scalar functions

More Information
The driver can completely handle all updating of data via SQL statements and the SQLExecute or SQLExecDirect calls, including BLOB data. Parameters are also completely supported, including BLOB parameters.

The driver provides scrollable cursor support via SQLFetchScroll and SQLExtendedFetch. The only two types of scrollable cursors supported are Static and Dynamic. Keyset-Driven cursors are not supported.

The driver cannot performed positioned updates using the SQL syntax WHERE CURRENT OF and using the SQLSetCursorName and SQLGetCursorName calls. This functionality is not supported in DBISAM.

Even though the driver supports parameter arrays, you still cannot request multiple result sets with the SQLMoreResults call. This is not supported in DBISAM.

If any of the DBISAM tables being accessed via the ODBC driver has an index that includes the special DBISAM RecordID field, it is possible that you could encounter an error (sometimes fatal) in the client application. This is due to the fact that the RecordID field is virtual and doesn't actually exist in the parent table. The DBISAM ODBC Driver takes the proper steps to inform the client application that this is the case by flagging the field as a "pseudo-column" in the index catalog information returned by the driver. However, some client applications appear to not pay any attention to this flag at all.
Image