Using InstallShield Express with dBASE Plus
By Paul Van House, Binx Custom Software and Senior Systems Analyst for Forged Vessel Connections in Houston, Tx.

Introduction

dBASE Inc. includes the INNO setup program on its dBASE Plus installation CD. But, as my wife sometimes points out, I’m a bit stubborn and set in my ways. Being a long-time dBASE/Clipper user I hate having to learn new tools if I don’t have to. That’s why I still prefer using the InstallShield Express program (ISX) that shipped with Visual dBASE 7. (It could also be the reason I don’t have a high-paying cutting edge job!)

I was at first concerned when I learned that both a new runtime engine and a new version of the Borland Database Engine (BDE) were a part of the dBASE Plus installation. But after only a few minutes experimenting I discovered that ISX works fine with the latest version of dBASE as well as the new version of the BDE.

The amount of work needed to make ISX work depends on how long it’s been since you upgraded your version of dBASE and ISX. If you are using ISX version 2.01 for Visual dBASE (VdB) then you are in luck! This is the version that shipped with VdB 7.01. I haven’t tested previous versions, but I will take other authors’ words at face value: “If you are using the version of ISX that shipped with Visual dBASE 7.0, the following instructions will not work.” To check your ISX version, open ISX and click Help|About. The version number appears just above the OK button near the bottom of the window.

OK, so you’ve verified that you are using ISX version 2.01. If you upgraded directly from VdB 7.01 to dBASE Plus, or if you did not install the ISX patch that was needed to allow ISX to install BDE version 5.x, please follow the instructions provided by Michael Rotteck and apply the patch before continuing in this document. Click English or German for information on applying this patch.

Registry Changes

This information is based on registry entries required for the runtime installation from the initial release of dBASE Plus. Once the CD is released, some of this may change!

This step may not be absolutely necessary, but I found it will work best if you create a new registry value in addition to the values placed by the default installation to point to the location of the current dBASE Plus runtime files. I discovered this need after test-installing a new executable and the installation program modified the default path for the runtime files from the dBASE Plus installation folder to the Windows system folder. The system folder, of course, is where you want the runtime files to go on an end user’s machine. To paraphrase the legendary M$ warning: please be aware that changing the registry can completely screw up your system so be careful!

- First, start the Windows Registry Editor (Click Start|Run, then key in `regedit` and click the OK button.)
- Now, navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\dBASE\PLUS\series1
- With the series1 key highlighted in the left pane, right-click in an empty area of the right pane and choose New then String Value

- A new value should appear in the right pane called New Value #1. Change the name of this value to `ISX_Install`
- Now double click on the ISX_Install entry to edit the value
- In the Value data entryfield, key in the path to the dBASE Plus Runtime folder created during installation and click OK to save the changes. The default is `C:\Program Files\dBASE\PLUS\Runtime` — your installation may have a different path!

Modify Swdepend.ini

Next, modify the file Swdepend.ini, which is used by ISX to locate runtime and BDE files needed by your dBL program. Either follow the instructions below, or click here to download a zip file containing an updated Swdepend.ini file with the changes already made.

- Find the file Swdepend.ini and make a backup copy. (Default location is C:\Program Files\Installshield\IS Express For Visual dBASE)
- Open Swdepend.ini in Notepad or any other text editor and find the section header`[VdBase Support]`
- Modify the following entries in this section as follows:
- Change the line that begins with `src=HKEY...` to read:`Src=HKEY_LOCAL_MACHINE\Software\dBASE\PLUS\series1\ISX_Install`
Place a semi-colon (comment indicator) and a space before the line that reads `SrcSub=bin`
Change the `Uses1=` line to read `Uses1=PLUSRUN.EXE`
Change the `Uses2=` line to read `Uses2=PLUSr_en.DLL`
- When you finish, your`[vdBase Support]` section should be as follows:

| `[vdBase Support]` `Src=HKEY_LOCAL_MACHINE\Software\dBASE\PLUS\series1\ISX_Install` `; SrcSub=Bin` `Uses1=PLUSRUN.EXE` `Uses2=PLUSr_en.DLL` `Uses3=RESOURCE.DLL` `Uses4=CTL3D32 FILE`
| ``

Important Note: The `Uses2=` setting will change depending on the language you are using:

> `Uses2=PLUSr_en.DLL` (English Version)
> `Uses2=PLUSr_de.DLL` (German Version)
> `Uses2=PLUSr_es.DLL` (Spanish Version)
> `Uses2=PLUSr_fr.DLL` (French Version)
> `Uses2=PLUSr_it.DLL` (Italian Version)
> `Uses2=PLUSr_ja.DLL` (Japanese Version)

Updating Current ISX Installation Scripts

In addition to updating you current ISX installation scripts to include files compiled with dBASE Plus, you also need to

- Uncheck and re-check the Visual dBASE Runtime checkbox in the ISX General Options Window. This will unload the previous runtime files and load the new runtime files.

- Since dBASE Plus also ships with an updated version of the BDE, you will also need to uncheck and recheck the BDE (Borland Database Engine) box. This will ensure that the current version of the BDE loaded on your computer will be installed with your application. Important Note: Unchecking this box will destroy any BDE aliases you may have set up in your installation script. Once you re-check this checkbox, be sure to click the Settings… button and re-create any aliases you may need to include in your installation.

ISX Installation Script Registry Changes

For new and existing installation scripts, I have discovered you will need to include a new Registry setting in your ISX script. This setting will allow creation of a key and value that will tell the end-user’s computer where to find the dBASE Plus runtime files.

- Click the Keys setting in the ISX Setup Checklist, located in the Make Registry Changes Section.
- Expand the HKEY_LOCAL_MACHINE key.
- Expand the Software key
- Expand the dBASE key
- You will likely now see a key named Visual dBASE or Visual dBASE 7.5 If you are creating a script for a dBL application that uses ONLY dBASE Plus generated files, you may safely delete these keys.
- Click on the dBASE key then click the Add Key… button.
- Name the new key `PLUS` then click the OK button

- Now click on the PLUS key, then click the Add Key… button.
- Name the new key `series1` then click the OK button.

- Click on the series1 key then click the Registry - Values tab, then the Add Value… button.
- Make sure the String radiobutton is selected, then name the value `RuntimePath` and key in`<WINSYSDIR>` for the Value Data.

- Click OK until you return to the ISX Setup checklist.

A previous document indicated that once you change these registry settings, they will become the default for all installations. I have not found that to be true. I have found it necessary to delete the old Visual dBASE 7.5 key and re-create the new keys for each new installation script I create.

Final Words

Whenever there is an update to the dBASE Plus runtime files, be sure they are copied to the folder’s “Runtime” Subfolder (default: C:\Program Files\dBASE\PLUS\Runtime) so the ISX script pulls the latest files, and to your Windows System folder so your deployed executables work from the latest version.

This document is based on previous works by Jean-Pierre Martel, Michael Rotteck, and Ken Mayer.