When you begin the install of Approach 97 on Windows 2000 or XP, it advises that it is not designed to run on the current operating system, and that certain functions will not work. I repackaged this into .msi format for a client who is on 2000/XP and is still dependent on some legacy Approach databases. With testing, I found that it was fully functional provided that the clients databases only required the default Approach ODBC drivers. Other optional ODBC drivers proved difficult if not impossible to properly capture and incorporate into a package.
Per User / Per Machine Info
In Approachs native install format, it is strictly a per user installation. SmartIcons and WebIcons within the Approach GUID are dependent upon HKCU registry entries. Therefore, be sure to run the application once and capture those registry entries. Make certain that a keypath is defined in the HKCU branch so that a self-heal occurs for a first time user. This will insure all the programs icons are present and work for each user. If you are familiar with the technique, move the HKCU keys into a component that is assigned to a parent feature, and place the remainder of the package in a child feature.
When you begin the install of Approach 97 on Windows 2000 or XP, it advises that it is not designed to run on the current operating system, and that certain functions will not work. I repackaged this into .msi format for a client who is on 2000/XP and is still dependent on some legacy Approach databases. With testing, I found that it was fully functional provided that the client’s databases only required the default Approach ODBC drivers. Other optional ODBC drivers proved difficult – if not impossible – to properly capture and incorporate into a package.
Per User / Per Machine Info
In Approach’s native install format, it is strictly a “per user” installation. “SmartIcons” and “WebIcons” within the Approach GUID are dependent upon HKCU registry entries. Therefore, be sure to run the application once and capture those registry entries. Make certain that a keypath is defined in the HKCU branch so that a self-heal occurs for a first time user. This will insure all the program’s icons are present and work for each user. If you are familiar with the technique, move the HKCU keys into a component that is assigned to a parent feature, and place the remainder of the package in a child feature.
For those of us cursed to *still* have Lotus Approach databases in production, there is at least some basic command line switches that you can use to automate installs.
We have the floppy-disk version of Approach copied onto a network drive, as opposed to the Smartsuite CD; just in case that's relevant, I assume the Smartsuite disc will have a separate approach installer which will work the same way though.
For those of you installing Approach off the Smartsuite CD, I did bump into this page, which may be of use to you, but I haven't tested it.
https://sharepoint.uvm.edu/sites/ad/distribution/appconfig/Lotus%20Approach.aspx
The install.exe file has the following valid switches:
/A <Path to Response File>
- Automates the installer, using options supplied in the response file.
/U "<Specify User Name>"
- I didn't end up using this switch, I presume it just changes the username in step 1 of the installer.
/?
- Brings up a help screen which tells you these switches.
In the same directory as the install.exe should be a file called "INSTAPR.RSP". This is the response file that the /A switch will be looking for. It is well commented and should be easy to customize to your needs.
Example command line for automatic install:
INSTALL.EXE -A "\\servername\data\Applications\Lotus Approach\INSTAPR.RSP"
Note that the interface will still appear using this method, but won't require any interaction.
We also needed to install the smartsuite patch; ssupdate.exe. I was unable to completely automate this with switches, but by adding the drive letter to the end of the command, it will at least apply the update automatically (But requires the user to click "OK" at the end.)
Example command line for automatic install:
ssupdate.exe C
This website uses cookies.
By continuing to use this site and/or clicking the "Accept" button you are providing consent
Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our
websites or when you do business with us. For more information about our
Privacy Policy and our data protection
efforts, please visit
GDPR-HQ
