WDINST: installing additional elements

WINDEV, WEBDEV AND WINDEV MOBILE
ONLINE HELP

Version:

Home | Sign in | English

Help

Editors

Installing applications and sites

WINDEV application

Setup editor

WDINST: installing additional elements

Overview

Install the distributable WINDEV tools

Distribute MDAC and DCOM 95

Install and configure the ODBC driver

Include an automatic uninstaller

See also

WDINST: installing additional elements

Overview

By default, only the files found in the "List of setup files" window are installed on the user computers.

The setup editor WDINST gives you the ability to:

Install the distributable WINDEV tools.
Distribute MDAC and DCOM 95.
Install and configure the ODBC driver.
Include an automatic uninstaller.

Note: These options can also be configured in the wizard for creating the setup program.

Installing additional elements
The management of the additional elements to install is performed in WDINST ("Tools .. WDINST - Setup editor").The management of the additional elements to install is performed in WDINST: on the "Tools" pane, in the "Utilities" group, click "WDInst". The wizard for creating the setup program also allows you to install additional elements.

Install the distributable WINDEV tools

Overview

Several WINDEV tools can be freely distributed with your applications:

Tools	Description

Versions 17 and later DplViewer New in version 17 DplViewer DplViewer	Used to view the duplicate copies.
ReplicSynchro	Used to manage the assisted Universal Replication.
WDConver	Converts the external files into HyperFileSQL files.Converts external files to HFSQL files.
WDDebug	Used to debug an application remotely
WDLog	Saves and restores the data files in HyperFileSQL format and manages the logs.Saves and restores the data files in HFSQL format and manages the logs.
WDOptimizer	Optimizes the access to the HyperFileSQL files (reindex, corrections of memos, ...).Optimizes the access to HFSQL files (reindexing, memo corrections, ...).
WDReplic	Manages the replication of data between several computers that use the same application.
WDRemoteAccessServer (or WDRPCServer)	RPC server allowing you to use the remote access on HyperFileSQL files.RPC server allowing you to use the remote access on HFSQL files.
WDSQL	Used to define a connection and to create queries in SQL code on this connection.
WDSvgApp	Used to save and restore the application. This tool is run by the automatic menu ("Save the application").
WDTelDiagno	Returns the list of available TAPI lines and specifies the line that will be used by the telephony functions.
WDTrans	Used to cancel transactions or to free records in transaction.

To limit the multiplication of applications on the end-user computer, the files required by these tools will be installed in the "\Program Files\Common files\ PC SOFT\25.0" directory. The path of the directory of optional tools is returned by SysDir. For example: SysDir(srCommonProgramFiles)+"\PC SOFT\25.0".

If an application shortcut is created in the "Start" menu, the shortcut of each tool installed on the user computer will also be added to the "Start" menu (in the same program group as the application).

The HyperFileSQL optimizer will be installed by default if the application is associated with a HyperFileSQL database.The HFSQL optimizer will be installed by default if the application is associated with a HFSQL database.

To install the distributable WINDEV tools on the user computers:

Select "Parameters of setup .. Advanced parameters".
Check "Include the optional tools when creating the setup".
Click the "Tools" button to select the tools to include.
Select the tools to include and validate.

Note: If you install a WINDEV tool without using WDInst, the following files must be supplied to the users:

The executable program of the tool (".EXE" file).
The WINDEV libraries ("wd250XXX.DLL" files).
The component files (".WDK" files) found in the "Programs" sub-directory of the setup directory of WINDEV.

Distribute MDAC and DCOM 95

Overview

If your application is using a database via OLE DB, the following elements must be installed on the user computers:

an OLE DB provider ("MSDAORA", "OraOLEDB.Oracle", "SQLOLEDB", ...).
MDAC (Microsoft Data Access Component) version 2.6 or later.

If MDAC is not installed, only the connection to the OLE DB database will be possible: it will not be possible to read the tables (a message indicates that this interface is not supported).

If Windows 95 is used on the user computers, DCOM 95 must be distributed in addition to MDAC.

Caution: The distribution license of MDAC and DCOM 95 specifies that the executables of MDAC and DCOM 95 must be downloaded (from the Microsoft Web site) in order to get the rights to redistribute them with an application. Before performing the operations described in the following paragraphs, you must download the executables of MDAC and DCOM 95 onto the current computer.

The executables of MDAC and DCOM 95 can be downloaded from the Microsoft Web site at the following addresses (valid when this document was published):

MDAC: http://www.microsoft.com/data
DCOM: http://www.microsoft.com/com/tech/dcom.asp

Distributing the MDAC executable to the users

To distribute the MDAC executable to the users:

Select "Parameters of setup .. HyperFileSQL files".Select "Parameters of setup .. HFSQL files".
Check "Install MDAC found at the following location".
Specify the path of the MDAC executable that was downloaded beforehand.

Distributing the DCOM 95 executable to the users

To distribute the DCOM 95 executable to the users:

Select "Parameters of setup .. HyperFileSQL files".Select "Parameters of setup .. HFSQL files".
Check "Install DCOM 95 found at the following location".
Specify the path of the DCOM 95 executable that was downloaded beforehand.

Install and configure the ODBC driver

Overview

To handle a HyperFileSQL database from a non-WINDEV application, the ODBC driver for HyperFileSQL must be installed and configured on the user computer. See ODBC driver on HyperFileSQL for more details.

Note: The ODBC driver on HyperFileSQL is used to read and write in a HyperFileSQL database from a non-WINDEV application.

To handle a HFSQL database from a non-WINDEV application, the ODBC driver on HFSQL must be installed and configured on the user computer. See ODBC driver on HFSQL for more details.

Note: The ODBC driver on HFSQL can only be used to read and write in a HFSQL database from a non-WINDEV application.

Install and configure the ODBC driver

To install and configure the ODBC driver:

Select "Parameters of setup .. HyperFileSQL files".Select "Parameters of setup .. HFSQL files".
Check "Install the ODBC driver for HyperFileSQL".Check "Install the ODBC driver for HFSQL".
Enter the name used to identify the HyperFileSQL database when using the ODBC driver for HyperFileSQL.Enter the name used to identify the HFSQL database when using the ODBC driver on HFSQL.
Enter the path of the analysis used as ODBC source (.WDD file corresponding to the WINDEV analysis).

Include an automatic uninstaller

Overview

To simplify the uninstall process of your application, WDINST allows you to include an uninstaller in the setup program.

In this case, the "uninst.INF" file will be created in the setup directory of the application. This file lists all the application files installed on the current computer.

Note: To uninstall the application, the uninstaller is using an entry in the registry. The setup editor WDINST allows you to modify this identifier. See Modifying the identifier used to uninstall the application for more details.

Uninstalling your application

As for any Windows application that includes an uninstaller, to uninstall an application, you must:

display the list of programs installed on the current system ("Add/Remove programs" in the control panel).
select the application in the list of programs.
click the "Modify/Delete" button.
The following elements will be deleted:
- the files listed in the "uninst.INF" file.
- the entries in the registry created when installing the application.
- the application shortcuts (on the desktop and in the "Start" menu) if they exist.
- the data files (".FIC", ".MMO" and ".NDX" files) after user confirmation.
- the files saved during the different updates (if they exist) after user confirmation.
- the directories whose files are deleted during the uninstall process.

Special case: If the application creates data files in a specific directory (different from the sub-directories of the application), these data files will not be automatically deleted during the uninstall process.

Note: You have the ability to translate the different messages of the uninstaller. See Translating the uninstaller for more details.

Including an uninstaller in the setup program

To include an uninstaller in the setup program:

Select "Parameters of setup .. End of setup".
Check "Include the uninstaller".