By default, 32-bit versions of Windows use the 32-bit ODBC Administrator, and 64-bit versions of. Applications and the 32-bit DBISAM ODBC Driver. Custom Driver Installation. For the DBISAM 4 ODBC Driver. In order to configure 32-bit drivers on 64-bit Windows.

Start display at page:

Download 'DBISAM Version 4 ODBC Driver Manual'

Neil Hunt
3 years ago
Views:

Transcription

1 Table of Contents DBISAM Version 4 ODBC Driver Manual Table Of Contents Chapter 1 - Before You Begin Application Compatibility 1 Chapter 2 - Using the ODBC Driver Configuring a Data Source Registry Entries Connection Strings Custom Driver Installation 15 Preface

2 Table of Contents This page intentionally left blank Preface

3 Before You Begin Chapter 1 Before You Begin 1.1 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: Page 1

4 Before You Begin Application Crystal Reports Versions and Notes 8.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 Office 2000 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 Visio Borland Database Engine (BDE) 2000 and later 5.01 and later ODBCExpress 5.06 and 7 With the BDE there are problems with using an autoincrement 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. Microsoft IIS ASP 5 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 Basic 6 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.NET 2002 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 Page 2

5 Before You Begin 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. Page 3

Windows 7 ultimate 32 bit free download. A user can choose the Best theme for its Desktop setting just by selection and click a new theme change as the user want.

6 This page intentionally left blank Page 4

7 Chapter 2 Using the ODBC Driver 2.1 Configuring a Data Source Introduction A data source, or DSN (Data Source Name), is used by applications that use ODBC to locate and access a specific database in a specific location. Once you have configured a data source in the ODBC Administrator, you may use this data source name in any application that can access ODBC. However, you should check out the Application Compatibility notes in this manual for more information on applications that have been specifically tested with the DBISAM ODBC Driver. Step-By-Step Instructions Complete the following steps to properly configure a data source that uses the DBISAM ODBC Driver: 1) Run the ODBC Administrator (odbcad32.exe). This program is located in the Start menu under Programs/Administrative Tools/Data Sources (ODBC). Note By default, 32-bit versions of Windows use the 32-bit ODBC Administrator, and 64-bit versions of Windows use the 64-bit ODBC Administrator, when launching the ODBC Administrator via the Administrative Tools link. If you're using a 64-bit version of Windows, then you must use the 32- bit ODBC Administrator located here in order to configure 32-bit data sources for use with 32-bit applications and the 32-bit DBISAM ODBC Driver: <WindowsInstallDir>SysWoW64odbcad32.exe where <WindowsInstallDir> is the base Windows installation directory, usually c:windows. 2) If you want the data source to be accessible by all users, then click on the System DSN tab. If you want the data source to only be accessible to the current user, then click User DSN tab (the default page). 3) Click on the Add button to begin adding a data source. This will bring forward a dialog with a list of the installed ODBC drivers. Select the DBISAM ODBC Driver from the list and click on the Finish button. Note It is possible that there may be more than one DBISAM ODBC Driver listed due to multiple, different major versions of the driver being installed on the system. 4) A DBISAM ODBC Driver configuration wizard dialog will now be shown. Follow the instructions on this wizard to complete the data source configuration. Page 5

8 If at any time you wish to re-configure the data source, simply choose the appropriate tab page (User DSN or System DSN), select the data source name that you previously added from the list of data sources, and then click on the Configure button. This will bring forward the same configuration wizard dialog as before, except in this case you cannot specify a name for the data source. Page 6

9 2.2 Registry Entries Location ODBC data sources are stored in the registry in Windows. The location of both user and system data sources is detailed below: Data Source Type User DSN System DSN Location HKEY_CURRENT_USERSoftwareODBCODBC.INI<Data Source Name> HKEY_LOCAL_MACHINESoftwareODBCODBC.INI<Data Source Name> Also, a list of data sources defined on the system can be found here: Data Source Type User DSN System DSN Location HKEY_CURRENT_USERSoftwareODBCODBC.INIODBC Data Sources HKEY_LOCAL_MACHINESoftwareODBCODBC.INIODBC Data Sources 64-bit Windows Under 64-bit Windows, the above registry keys/values are for 64-bit DSNs only, and are only configurable via the 64-bit ODBC Administrator that is accessible from the Control Panel. In order to configure 32-bit DSNs on 64-bit Windows, one must use the 32-bit ODBC Administrator located here: <WindowsInstallDir>SysWoW64odbcad32.exe where <WindowsInstallDir> is the base Windows in

Dbisam Odbc Driver 64 Bit Download