Public Beta: dbExpress Informix IDS 9.2 driver

By: John Kaster

Abstract: You can now download a beta test version of the new dbExpress driver for Informix for use with Delphi 6 or C++ Builder 6 Enterprise

Description of Public Beta

dbExpress Informix IDS 9.2 beta driver for Delphi 6 Enterprise and C++Builder 6 Enterprise

Bugs Fixed/New Features

This is a new dbExpress driver for Informix, so everything is new with it.

Downloading the beta

Because this is a public beta, you must agree to a disclaimer before downloading the file containing the update. When you attempt to download the file, you will be asked if you agree to the disclaimer. The file is then streamed directly from the web server. This streaming process normally prevents auto-resuming the file with a download manager. The file is currently 54K. We apologize for any inconvenience this may cause if your download gets interrupted.

You can download this file from CodeCentral. The direct link to download the file is http://codecentral.borland.com/codecentral/ccweb.exe/listing?id=17693. The zip file download is 54K.

This file may be updated from time to time, and you can look at the detail listing for the file to find out when it was last updated, or any other specific notes regarding changes to this beta.

Installation

Because this is a beta version, you should back up the current, shipping version of the files you will be replacing with the files contained in this beta so you can restore them without having to re-install the entire product.

Special installation instructions

  • Install the Informix client software
  • copy the dbexpinf.dll in to DELPHI\BIN
  • make the changes described below to your dbxdrivers, dbxconnections ini files
  • To connect to Informix IDS 9.2 from Delphi 6 Enterprise or C++Builder 6 Enterprise, add these entries to your dbxdrivers.ini and dbxconnections.ini. Make sure you have installed the Informix client software and can connect to the server using ILogin.

    Note: The Informix client library is statically linked to this driver so the VendorLib name in the dbxdrivers.ini really doesn't matter.

    Add the following to dbxdrivers.ini

    [Installed Drivers]
    Informix=1
    
    [Informix]
    GetDriverFunc=getSQLDriverINFORMIX 
    LibraryName=dbexpinf.dll
    VendorLib=isqlb09a.dll
    HostName=ServerName
    DataBase=Database Name
    User_Name=user
    Password=password
    BlobSize=-1
    ErrorResourceFile=
    LocaleCode=0000
    Informix TransIsolation=ReadCommited
    

    Add the following to dbxconnections.ini

    [InformixConnection]
    DriverName=Informix
    DataBase=Database Name
    User_Name=user
    Password=password
    BlobSize=-1
    ErrorResourceFile=
    LocaleCode=0000
    Informix TransIsolation=ReadCommited
    

    Testing

    Borland is planning to release a certified version of this beta software in the future. We are providing it as a public beta to have as broad a base as possible for testing it before we certify it. This is specifically why we have made this file available for our customers to download.

    Special testing instructions

    Most data-access functionalities should work. However, there's a known bug with Web applications with a "Connection name in use" error.

    Warnings

    We have performed tests to verify that the software you may be downloading and testing works as intended. However, you may still encounter problems with using this version of the software. It has not yet been certified. Please read the disclaimer you see when downloading the file very carefully, as it provides details on Borland's legal position with respect to this public beta.

    Specific warnings:

    This is a public beta so use it for testing only

    Feedback

    Please provide feedback on this beta to the borland.public.delphi.database.dbexpress. If you cannot access our newsgroups with a conventional newsgroup reader, you can use a browser to access this newsgroup at http://newsgroups.borland.com.

    If you encounter problems with this beta product, please provide as much detail as possible in the newsgroup message, including the platform you are running on and steps to reproduce the problem.

    If you are uncertain how to configure newsgroup access, please refer to Borland's newsgroup reference pages.


    Server Response from: ETNASC01