ADSM-L

Re: ODBC Driver

2001-11-12 06:10:43
Subject: Re: ODBC Driver
From: Zlatko Krastev/ACIT <acit AT ATTGLOBAL DOT NET>
Date: Mon, 12 Nov 2001 13:08:56 +0200
And this can be easily avoided:
1. double-click
2. the .exe extracts the installation files
3. setup.exe is auto-fired
4a. setup.exe finds MDAC is not correct version and fails with message box
about the fact
4b. setup.exe is satisfied by MDAC version and ODBC is installed
5. extracted files are deleted.
Thus both installations will have similar behavior and chances for
confusion will be less. And "That's something we can consider for future
releases.". So wait for a while and it will come for free ;-)

Zlatko Krastev
IT Consultant





Gerald Wichmann <gwichmann AT SANSIA DOT COM> on 06.11.2001 21:30:53
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: ODBC Driver

Theres no real difference in the scenarios you present but that's not
really what we were discussing either. We were comparing installing the
BA Client to the ODBC driver.

BA client:

Doubleclicking on the .exe will cause it to unpack and automatically run
setup.exe so you can continue with the installation. i.e. after it
unpacks you don't have to manually go find the setup.exe file and run it
yourself because the packaged BA Client does it for you.

ODBC driver:

Doubleclicking on the .exe will cause it to unpack into a fairly obscure
default directory and then exit. The setup.exe file doesn't
automatically launch for the reasons Andy explained below. Thus you have
to go find the setup.exe file and figure this out. Initially when you
doubleclicked the .exe it's not entirely clear whether the driver was
installed or not (it wasn't). If you just installed the BA Client
beforehand, you may very well assume it did. Thats where the confusion
comes up.

Gerald Wichmann
System Engineer
StorageLink
408-844-8893 (v)
408-844-9801 (f)


<Prev in Thread] Current Thread [Next in Thread>