OK, please send or attach the current InnoSetup install that you are using.

Dave

Dave,

<< OK, please send or attach the current InnoSetup install that you are
using. >>

Attached.  We use double-quotes around all path names, etc., so that may
have something to do with the difference in behavior.  I noticed that your
setup script didn't use double-quotes around the values in the script.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

I couldn't find any instance of the double quotes.  Can you please clarify?

Thanks

Dave



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Dave,

<< OK, please send or attach the current InnoSetup install that you are
using. >>

Attached.  We use double-quotes around all path names, etc., so that may
have something to do with the difference in behavior.  I noticed that your
setup script didn't use double-quotes around the values in the script.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dave,

<< I couldn't find any instance of the double quotes.  Can you please
clarify? >>

Here's an example of using the double-quotes around the key name and value
names.

Root: HKLM; SubKey: "Software\ODBC\ODBCINST.INI\DBISAM 3 ODBC Driver";
ValueType: string; ValueName: "APILevel"; ValueData: "1"; Flags:
uninsdeletekey

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

IS Tool automatically strips the quotes, and I believe the InnoSetup compiler treats both ways of specifying the data identically (I tried compiling under IS Tool and directly
under the compiler and the installer was the same).

I have given up.

Dave,

<< IS Tool automatically strips the quotes, and I believe the InnoSetup
compiler treats both ways of specifying the data identically (I tried
compiling under IS Tool and directly under the compiler and the installer
was the same).

I have given up. >>

Did you try installing the ODBC driver into your desired directory using
*our* installation setup program ?  Did it work ?

--
Tim Young
Elevate Software
www.elevatesoft.com