*************************** D3 ODBC Client Installation Version: 2.0.35 November, 2011 *************************** ***IMPORTANT NOTE*** The 64 bit version of C35 installs both the 64 bit and 32 bit versions of the ODBC driver. If you have the 64 bit version of C34 installed, you must uninstall both the 64 bit and 32 bit versions of the C34 ODBC driver before installing the 64 bit version of C35. ---------------------------------------------------- Before running the D3 ODBC Client Installation, reboot the machine. This installation will install the latest version of the D3 ODBC Driver, 2.0.35 and the latest version of the D3 Class Library (ODBC Only). -------------------------------------------------- If you are using the C35 Driver to connect to a D3 7.5 or earlier release, you must specify an IPv4 address or hostname for the host textbox when defining a datasource. Otherwise, a connection cannot be made. For Developers Using Visual Basic 4.0 ------------------------------------- Since the library is built using VB 6.0, developers using Visual Basic 4.0 need the VB 6.0 runtime, MSVBVM60.DLL (service pack 2 or higher). This DLL can be downloaded from the Rocket FTP site at ftp://ftp2.rocketsoftware.com/pub/ODBC/2.0.x/Releases. Once the DLL is downloaded, register the DLL using regsvr32 (regsvr32 msvbvm60.dll). Run (or rerun) the D3 ODBC Client Installation. For Developers Using Visual Basic 5.0 ------------------------------------- Since the library is built using VB 6.0, developers using Visual Basic 4.0 need the VB 6.0 runtime, MSVBVM60.DLL. This DLL can be downloaded from the Rocket FTP site at ftp://ftp2.rocketsoftware.com/pub/ODBC/2.0.x/Releases. Once the DLL is downloaded, register the DLL using regsvr32 (regsvr32 msvbvm60.dll). Run (or rerun) the D3 ODBC Client Installation. If in doubt, to verify that a file MSVBVM50.DLL is at a level of SP2 or higher, right click the file from Windows Explorer, select Properties, then Version. If something similar to "05.00.4319 (SP2)" displays, then the DLL can be used with the latest version of the client. Visual Basic 6.0 ---------------- To use the latest version with VB6.0, the file MSVBVM60.DLL must be registered on the system. Because the C35 ODBC client is built on Visual Basic 6 as opposed to the C27 client (which was built on Visual Basic 5) all Visual Basic executables must be rebuilt in order to use the latest version of the ODBC client. All older version of the D3 ODBC client should be unregistered. From the system32 directory type: regsvr32 d3clodbc.dll -u This will unregister the older D3 ODBC client. ============= Upgrade Notes ============= ------------------------------------------------------------- The following sections are for users upgrading from D3 ODBC clients prior to version 2.0.24 ------------------------------------------------------------- Login Timeout ------------- As of version 2.0.24 of the D3 ODBC Driver, the D3 Data Source Configuration Parameters dialog box includes a 'Login Timeout'. This text box includes the time in seconds that the driver will wait for a login request to complete before returning control to the client application. The range of the 'Login Timeout' is 1 to 32767 seconds. A 'Login Timeout' of 0 is equivalent to the maximum timeout of 32767 seconds. For programmers using the ODBC API, specifically SQLConnect and SQLDriverConnect, in the event of an error, SQLError will return SQLState S1T00 with a message 'Login Timeout expired.'. For additions and changes to errors returned after a failed connection, see the next section 'Connection Errors'. For programmers using the D3 Class Library (ODBC Only), specifically brOpenConnection, the trappable error 'd3MiscErr_Timeout' indicates that the connection failed because the timeout expired. For additions and changes to errors returned after a failed connection, see the next section 'Connection Errors'. Connection Errors ----------------- As of version 2.0.24, the errors returned after a failed connection have been expanded and modified. The following table supplies a description of common connection errors, the errors returned via SQLConnect or SQLDriverConnect and the trappable errors available in the D3 Class Library (ODBC Only). A + indicates that this is an addition to the possible errors returned. The () indicates the error returned prior to version 2.0.24. ODBC API D3 Class Library Description SQLState Trappable Errors ----------- -------- ---------------- Invalid D3 user, account or password 28000 d3MiscErr_NoConn Out of ports or users 28000 d3MiscErr_NoConn Non-existent or invalid DSN IM002 d3MiscErr_InvalidDSN+ (d3MiscErr_NoConn) No server started 08001 d3MiscErr_NoServer+ (d3MiscErr_NoConn) Virtual machine not found 08S01+ d3MiscErr_NoServer+ Timeout expired S1T00+ d3MiscErr_Timeout+ Server abort, shutdown or reset 08S01+ d3MiscErr_NoServer+ (d3MiscErr_Internal) Unknown network or server errors S1000 (08S01) d3MiscErr_NoServer+ (d3MiscErr_Internal) ------------------------------------------------------------- The following sections are for users upgrading from D3 ODBC clients prior to version 7.1.C12 ------------------------------------------------------------- D3 Class Library (ODBC Only) ----------------------------------------- D3 Class Library (ODBC Only) is now the name for the library previously known as the D3 VB ODBC Object Library. Versions 7.1.C12 through 2.0.C28 were built in Visual Basic 5.0. Versions 2.0.C30 is built in Visual BASIC 6.0. This DLL is now named, D3CLODBC.DLL (formerly called D3VBODBC.DLL). In the Visual Basic 'Available References', the library will appear as 'D3 Class Library (ODBC Only)'. Older copies of the library can be unregistered (using regsvr32 /u d3vbodbc.dll) and deleted if no longer needed. For developers with existing applications ----------------------------------------- To use the latest version of the D3 Class Library (ODBC Only), change the project references by deleting the reference to 'D3 VB ODBC Object Library' and including the reference to 'D3 Class Library'. The latest version of the library is backward compatible for code developed using previous versions of the library with ONE EXCEPTION: As of version C12, brOpenTclCommand only initializes the TCL command. brExecute must be called to execute the command. Previously, brOpenTclCommand initialized AND executed the TCL command. Therefore, developers with code containing brOpenTclCommand must add brExecute immediately following the brOpenTclCommand to maintain functionality.