Prior to Installing the ODBC Components of Centura Products

From Support Wiki

Jump to: navigation, search
3 July, 1997

Prior to Installing the ODBC Components of Centura Products

Problem Description:

Centura Software has discovered a problem with the ODBC installation routines that are part of the setup of SQLBase, Centura Team Developer, and Centura Web Developer. By choosing ODBC installation, you may overwrite more recent versions of some, but not all, of the ODBC component files. A symptom of this problem is that a message box will appear any time an ODBC-enabled application is started:

 

By clicking OK, an ODBC application appears to run normally though there is no guarantee this will always be the case. Clicking CANCEL will terminate the application.

The customers most likely to encounter this problem have installed some or all components of Office 97 (such as Access). This often comes preinstalled on newer systems. Office 97 ships with version 3.0 ODBC components. Centura products ship with version 2.5 components.

Problem Status:

Centura is tracking this problem as defect #62867A.

Recommendation:

To avoid this problem, Centura recommends one of two options:

   1. If ODBC components are not required, then choose to do a custom installation and deselect the ODBC components. Customers upgrading from a previous version of SQLBase can safely choose this option if gpgup09.dll is present and already at version 2.12.0000. This can be verified by checking the properties on the file or by viewing the SQLBase driver version in the ODBC Administrator utility. CTD/CWD customers can not skip installation of the ODBC components if they are using ODBC data sources such as Microsoft SQL Server in their applications. These customers and new SQLBase® installations should proceed as described below.
   2. If ODBC components are required, Centura recommends files named odbc*.* be backed up from \windows\system (on Win95) or \windows\system32 (on WinNT). Restore these files to their original location after the Centura product installation completes. This step should only be necessary if the ODBC files are presently newer than version 2.50.3006. If the version is prior to this, no extra work should be required and the ODBC components will be upgraded to this version. The version installed can be verified by checking the properties on the file 'odbc32.dll' found in the above named directory of the applicable operating system or by checking the version of the ODBC Driver Manager in the ODBC Administrator utility.

Check this web page periodically. As new information on the status of this problem becomes available, this web page will be updated. When a fix is released, information on how to obtain the fix will be posted here.

Problem Analysis:

The Centura installer invokes the standard Microsoft installer for the ODBC components included in Centura products. This installer is designed to check versions and only install these components when the existing files are from an earlier version. It is not understood at this point why this version checking fails during installation of a Centura product.

The message box displayed is indicative of the fact that not all the components were replaced, only some of them. In particular, the files ODBCCP32.CPL, ODBCCP32.DLL, ODBCINT.DLL, CTL3D32.DLL, and ODBCINST.HLP are replaced while other ODBC files are not.

Larry Johnson
Senior Staff Consultant
Centura Software