Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 6 of 6 total
Thread Renaming ODBC driver
Fri, Jun 27 2008 10:00 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

Hi,

If I rename the Version 4 ODBC Driver from "dbodbc.dll" to for example
"Cypher1Odbc.dll" then if I try and alter and existing DSN in the ODBC
Data source manager I get an error saying:

"The setup routines for the DBISAM 4 Driver ODBC driver cannot be found.
Please reinstall the driver".

Hoever if I have the default "dbodbc.dll" driver installed as well as my
own "Cypher1Odbc.dll" driver then all works as expected.

It is as iff it is looking for "dbodbc.dll" for the Setup functions
instead of "Cypher1Odbc.dll" as I have specified.

My registry settings are as follows:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\Cypher1 ODBC Driver]
"Driver"="D:\\Cypher1.net\\bin\\Cypher1Odbc.dll"
"Setup"="D:\\Cypher1.net\\bin\\Cypher1Odbc.dll"
"DriverODBCVer"="03.00"
"UsageCount"=dword:00000001



Chris Holland
Fri, Jun 27 2008 1:30 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Chris,

<< It is as iff it is looking for "dbodbc.dll" for the Setup functions
instead of "Cypher1Odbc.dll" as I have specified. >>

The data source registry settings also has an entry for the driver called
Driver.  Make sure that this is changed also.  The data source registry
settings can be found here:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
or
HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI

depending upon whether it is a user or system DSN.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 30 2008 4:09 AMPermanent Link

Chris Holland

SEC Solutions Ltd.

Avatar

Team Elevate Team Elevate

Hi Tim,

It appears that the Data Source entry attaches itself to an internal
name form the DLL. Even though I renamed the driver to Cypher1ODBC.dll
the data source is linked to "DBISAM 4 ODBC Driver", so I assume it
picked this up from the dll.

Not to worry, I was only renaming the driver to try and keep things tidy
I don't really need to do it.

Chris

Tim Young [Elevate Software] wrote:
> Chris,
>
> << It is as iff it is looking for "dbodbc.dll" for the Setup functions
> instead of "Cypher1Odbc.dll" as I have specified. >>
>
> The data source registry settings also has an entry for the driver called
> Driver.  Make sure that this is changed also.  The data source registry
> settings can be found here:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI
> or
> HKEY_CURRENT_USER\SOFTWARE\ODBC\ODBC.INI
>
> depending upon whether it is a user or system DSN.
>
Mon, Jun 30 2008 11:51 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Chris,

<< It appears that the Data Source entry attaches itself to an internal name
form the DLL. Even though I renamed the driver to Cypher1ODBC.dll the data
source is linked to "DBISAM 4 ODBC Driver", so I assume it picked this up
from the dll. >>

Yes, sorry about that - I forgot that bit.  That title is in the version
information, so if you modify the version information in the DLL, you can
change it to whatever you want.

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 30 2008 2:34 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Chris,

Shoot, I did forget one thing - in this key:

HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC Data Sources

You need to make sure that the DSN is mapped to the proper ODBC Driver
*name* also.

Perhaps that was the issue ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Mon, Jun 30 2008 3:08 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Chris,

Actually, axe that suggestion - the DSN configuration will set the driver
name back to that specified by the version info in the DLL, so yes, you'll
have to modify the version info.

--
Tim Young
Elevate Software
www.elevatesoft.com

Image