Hi

I recently purchased the ODBC driver and created an install using an Inno setup script posted elsewhere on this forum.

The installer appears to work, in that all of the entries in:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\My App ODBC Driver]

are identical to those in:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver]

However when i create a System DSN using "My App ODBC Driver" the driver is not set:

[HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\TEST_ODBC_DRIVER]
"Driver"=""

(all other registry entries are identical to the ODBC.INI entry created for a System DSN using the DBISAM 3 ODBC Driver).


This results in the error when starting the System DSN: The setup routines for the DBISAM 3 ODBC Driver ODBC Driver could not be found. Please reinstall the driver.


What have i missed?

Thanks

Dave

Dave,

<< I recently purchased the ODBC driver and created an install using an Inno
setup script posted elsewhere on this forum. >>

Thanks very much for the order.  As for the issue, could you post your exact
registry settings for the ODBC driver ?  If you don't want to post them
here, feel free to privately email them to me (timyoung@elevatesoft.com).

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks, i've sent it.

Hi Tim,

Did you receive my message?

Dave,

<< Did you receive my message? >>

No, I did not receive anything yet.  Perhaps we don't have your email
address on our whitelist that will allow you to send attachments.  In such a
case, the email will get blocked and you should get a failure notification
from your mail server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

OK, i've resent it using the address I've used on this forum.

Dave

> Tim wrote:
>
> << Here is my entire ODBC registry tree.... >>
>
> Everything seems to be in order.  I take it that the escaped backslashes and quotes are an artifact of the registry dump tool that you used ?

Yes, that is correct

> I would check to make sure that whatever user you're running the ODBC driver under has the proper rights to these registry entries

It's not just users, It also happens when I install it on our test machines.  It is consistent.

I have full administrator rights, Windows XP SP2.  There are no permissions issues.


> and the D:\ drive and directory where the ODBC driver is installed.

All the paths are absolutely correct.

I will send you the install script I am using so you can reproduce it on your system.

The install script creates the identical registry entries to yours (only the driver name and path differs), so the driver setup must be treating the customized install differently.

Dave

Dave,

<< The install script creates the identical registry entries to yours (only
the driver name and path differs), so the driver setup must be treating the
customized install differently. >>

I can assure you that the driver does not use any hard-coded path names,
driver names, etc.  You can try it yourself - just run our installation
routine and change the destination directory.  It will work just fine.

I've looked at your .ISS file, and it seems to be in order.  However, I
couldn't possibly use it without changing everything around to fit our
installation, and I'm sure that it will run just fine at that point because
it will look just like what I posted.

The only thing left that I can recommend is to try turning on tracing in the
ODBC administrator application and see if anything more specific shows up
when you try and use the ODBC driver.  If it does, then please post it here
or send it to me.

--
Tim Young
Elevate Software
www.elevatesoft.com

> I've looked at your .ISS file, and it seems to be in order.  However, I
> couldn't possibly use it without changing everything around to fit our
> installation, and I'm sure that it will run just fine at that point because
> it will look just like what I posted.


Hi Tim

I'm disappointed that you didn't bother to test my install.

If you had, you would have found that it installs under \Program Files\ and then you would have realized that the ODBC driver fails with a long path/path containing a space.

When I moved the drivers from:

C:\Program Files\LMK_ODBC

to

C:\LMK_ODBC

And updated the paths under ODBCINST.INI then it worked correctly.


Do you have an updated version of the v3.30 ODBC driver that supports long path names?

Dave

Dave,

<< I'm disappointed that you didn't bother to test my install. >>

This falls under "Inno Setup", not DBISAM.  The DBISAM 3.30 ODBC driver has
no problem with long path names and spaces, so it must have to do with your
Inno Setup script.  You can verify this by installing the stock 3.30 ODBC
driver to a direcory under the \Program Files\ directory.  I tried it with
"C:\program files\dbisam odbc std\ver3" and it works fine.

Unfortunately, I don't have time right now to help customers with their Inno
Setup scripts.  The best I can do is give you what we use and hope that you
follow it as closely as possible.

--
Tim Young
Elevate Software
www.elevatesoft.com