PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US

  • Overview
  • Configure the synchronization of deployed data (automatic modification of data files)
  • Index the HFSQL files during setup
  • Include the setup of a HFSQL Client/Server server
  • Configuring the location of application files
  • Notes
  • Installing an application that creates HFSQL Classic data files
  • Installing an application and its HFSQL Classic data files
  • Deploy the data files on a HFSQL server
  • Customize the location of the groupware files during setup
  • User groupware after version 18
  • User groupware before version 18
  • Including MDAC and DCOM 95 in the setup
  • Install the ODBC driver for HFSQL
  • Installing the OLEDB provider for HFSQL
  • Installing and configuring the modules for the assisted universal replication
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The wizard for creating the setup program takes into account the setup of database with the application and proposes different optional elements.
The additional modules for using a database allow you to add additional options to the setup program. The user will be able to access the advanced setup parameters.
You can:
Note: From version 19, HFSQL is the new name of HyperFileSQL.
Configure the synchronization of deployed data (automatic modification of data files)
If the option "Configure the automatic modification of data files" is checked, the automatic data modification will be performed when installing the current application.If the option "Configure the synchronization of deployed data" is checked, the automatic data modification will be performed when installing the current application.
The automatic data modification is used to update the description of the data files found on the user computers. For more details, see:
Note: if this option is checked, the automatic data modification will be performed (whether it is required or not). The automatic modification will have no effect on the application if it is performed on data that is already updated.
Index the HFSQL files during setup
The option "Index the HFSQL files during setup" is used to reduce the size of the setup program by deleting the index files from the setup program. These files will be automatically re-created on the end-user computer when the application is installed.
You have the ability to select the files for which the index files must be deleted.
Notes:
  • This feature is not available for the password-protected data files.
  • This feature is available for the HyperFileSQL Classic data files only. For the HFSQL Client/Server files, the configuration is performed via "Deploy data files on a HyperFileSQL server".This feature is available for the HFSQL Classic data files only. For the HFSQL Client/Server files, the configuration is performed via "Deploy data files on a HFSQL server".
Include the setup of a HFSQL Client/Server server
The option "Include the setup of a HFSQL server" is used to redistribute the setup of a HFSQL Client/Server server. See Installing a HFSQL Client/Server server for more details.
Configuring the location of application files
The option "Configure the location of the data files found in the application" is used to define the location of the data files found in the application.
The following connections are listed:
  • The connection named "Default location": This connection corresponds to the location of the HyperFileSQL Classic files found in the analysis and associated with no connection. By default, the data files are created in the directories specified when describing files in the analysis.
  • The connections defined in the analysis.
The connection information used by the application will be found in the ".WX" file found beside the executable.
The "Parameters" button is used to configure these connections if necessary:
  • If the option "All the connections use the same parameters" is checked, a single connection can be configured.
  • If the option "Each connection is configured independently" is checked, all the connections can be configured one by one.
The screen for configuring the connection allows you to:
  • use the values given in the project analysis.
  • use the values given in the.WER file (for a universal replication).
  • use new values. In this case, you have the ability to define a new connection with all characteristics.
  • use the values entered during the setup. In this case, the user will specify the data location when the application is installed. The default values proposed to the user can be typed in the configuration screen.
  • store the server parameters. This option is available only if the setup of a HFSQL server was included in the application setup.

Notes

  • If the parameters of the connection are modified between two setups, you have the ability to force the new parameters via "The above parameters will replace the values entered during a previous setup".
  • The SetupFile variable allows you to use the path of data files for HFSQL Classic files. The path used is the one defined in the HFSQL Classic properties of a connection to a HFSQL Classic database (ISAM).

Installing an application that creates HFSQL Classic data files

By default, the data files are created in the directories specified when describing files in the analysis. However, these directories can be modified:
  • when creating the executable of the application.
  • by programming with HSubstDir or HChangeDir.
  • when creating the setup program (setting of the connection named "Default location")
  • during the setup. The directory for creating the data files will be selected by the user.
If your application is using data files, you can allow the user to configure the location of the data files when installing the application. The directory selected by the user will be automatically used for all the data files created by the application.
Note: This directory will be proposed by default when installing the application updates. This option is used to avoid programming the location of data files (with HSubstDir for example).
Reminder: In any case, the directory for creating the HFSQL Classic data files is defined according to the following priority order:
  1. Directory specified by HSubstDir or HChangeDir.
  2. Directory selected when installing the application (if this option is proposed to the user).
  3. Directory selected when creating the executable.
  4. Directory specified when describing the files in the analysis.
Therefore, the directory defined by HSubstDir or HChangeDir has priority over all the other directories.

Installing an application and its HFSQL Classic data files

These data files are installed in the directory specified in the wizard for creating the setup program.
For a network setup, these data files will be installed in the "<ExecutableName>" sub-directory of the setup directory of the application on the server. This directory can be modified if necessary in the configuration screen of the connection named "Default location"
Deploy the data files on a HFSQL server
When creating the setup program of the application, you also have the ability to deploy the HFSQL Client/Server data files on the requested server via "Deploy the data files on a HFSQL server".
For each data file of the application, the "Properties" button allows you to specify:
  • the connection that must be associated with this data file.
  • the current location of the data file to install (location of the source data file).
  • whether the index must be copied or not. If the index is not copied, it will be automatically rebuilt during the setup. This option is used to limit the size of the setup program when the index file is quite large.
Note: The current location of the data files can correspond to the data files found on an accessible server or to the data files copied locally.
Customize the location of the groupware files during setup

User groupware after version 18

If your application supports the user groupware, the option "Customize the location of the groupware files during setup" is used to configure the location of data files for the User Groupware.
By default, these data files are created in the "GPW_<Application Name>" sub-directory of the setup directory of the application. However, this directory can be modified. The table below presents the different methods proposed by WINDEV to modify this directory.
How to modify the creation directory of these files?
  • When configuring the user groupware (caution: this directory is used for the tests of the application only).
  • When creating the executable of the application.
  • When installing the application. This directory is selected by the user.
What is the priority order when defining the creation directory of these files?
  1. The directory selected by the user when installing the application (if the setup program allows the user to select this directory).
  2. The directory selected when creating the application executable.
  3. The default directory ("GPW_<ApplicationName>" sub-directory of the setup directory of the application).
Therefore, the directory selected by the user has priority over the other directories.
To allow the user to configure the location of the files of user groupware, check "Customize the path of the files of user groupware during the setup".

User groupware before version 18

If your application supports the user groupware, two categories of files are managed:
  • The data files used to identify the users. These data files can be common to several applications.
  • The data files used to manage the rights granted to the users on the different windows of the application. These files are specific to the application.
See The files of user groupware for more details.
By default, these data files are created in the "GPW_<Application Name>" sub-directory of the setup directory of the application. However, this directory can be modified. The table below presents the different methods proposed by WINDEV to modify this directory.
Data files used to
identify the users
Data files used to
manage the rights granted to the users
How to modify the creation directory of these files?
  • When configuring the user groupware (caution: this directory is used for the tests of the application only).
  • When creating the executable of the application.
  • When installing the application. This directory is selected by the user.
  • When installing the application. This directory is selected by the user.
What is the priority order when defining the creation directory of these files?
  1. The directory selected by the user when installing the application (if the setup program allows the user to select this directory).
  2. The directory selected when creating the application executable.
  3. The default directory ("GPW_<ApplicationName>" sub-directory of the setup directory of the application).
Therefore, the directory selected by the user has priority over the other directories.
  1. The directory selected by the user when installing the application (if the setup program allows the user to select this directory).
  2. The default directory ("GPW_<ApplicationName>" sub-directory of the setup directory of the application).
Therefore, the directory selected by the user has priority over the default directory.
To allow the user to configure the location of the files of user groupware, check "Customize the path of the files of user groupware during the setup".
Including MDAC and DCOM 95 in the setup
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):
To distribute MDAC and DCOM 95 to the users:
  1. Check "Include MDAC in the setup".
  2. In the rest of the wizard:
    • Specify the path of the executable of MDAC. A link proposes to download the executable of MDAC from the Microsoft Web site.
    • Specify the path of the executable of DCOM 95. A link proposes to download the executable of DCOM 95 from the Microsoft Web site.
Note: The size of the setup program will be increased if MDAC is included in the setup. The setup program of MDAC will be the one found on the developer computer.
Install the ODBC driver for HFSQL
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 The 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.
To include the ODBC driver in the setup program:
  1. Check "Install the ODBC driver for HyperFileSQL".Check "Install the ODBC driver for HFSQL".
  2. In the rest of the wizard, enter the name used to identify the HFSQL database when using the ODBC driver on HFSQL.
Installing the OLEDB provider for HFSQL
To handle a HFSQL database from a non-WINDEV application, the ODBC provider on HFSQL must be installed on the user computer.
Note: The ODBC provider on HFSQL can be used to read and write in a HFSQL database from a non-WINDEV application.
To include the OLE DB provider in the setup program, check "Install the OLE DB provider for HyperFileSQL".To include the OLE DB provider in the setup program, check "Install the OLE DB provider for HFSQL".
Installing and configuring the modules for the assisted universal replication
If your application contains a description file for the assisted universal replication (.WER file), the setup wizard automatically proposes to configure the setup of the assisted universal replication.
Minimum required version
  • Version 11
Comments
Click [Add] to post a comment