Home | Sign in | English EN

  • Overview
  • Remarks
  • Names on a Linux server
  • Important
  • Managing the integrity constraints
  • Importing the structures
  • Limitations
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac CatalystUniversal Windows 10 App
Stored procedures
If you modify an existing WINDEV application into an HFSQL Client/Server application, two methods can be used to convert the HFSQL Classic files into HFSQL Client/Server files: from the data model editor or from the HFSQL Control Center. See Converting an HFSQL Classic database into HFSQL Client/Server for more details.
No specific operation is required to create an HFSQL Client/Server application. The data files will be created on the server during the call to HCreation or HCreationIfNotFound. Remark: From version 19, HFSQL is the new name of HyperFileSQL.
WINDEVWEBDEV - Server codeLinux

Names on a Linux server

On a Linux server, the names of data files must be written in lowercase with no accented characters.
Therefore, the file named "Tasks.fic" must be renamed to "tasks.fic". HCopyFile is used to copy the data files while taking into account the specific features regarding the case of file names in Linux.


In HFSQL Client/Server:
  • HSubstDir is ignored. Indeed, this function can only be used to substitute the directories of the HFSQL Network files.
  • If HChangeDir is used, you must specify a path relative to the directory of the application database on the server. This operating mode allows you to be independent of the location of the server used.
  • If a directory path is specified in the analysis description, in the description of the data files found in the analysis or in the project description, this path must be relative to the directory of the application database on the server.
  • The data files accessed by an HFSQL server are accessible via this server only. They cannot be directly accessed by another application especially via the HFSQL Classic engine. A connection to the server is required to access these data files.

Managing the integrity constraints

If an HFSQL ISAM application was modified into an HFSQL Client/Server application by creating the data files on the server, the integrity constraints are supported.
If an HFSQL ISAM application was modified into an HFSQL Client/Server application without creating the HFSQL data files on the server (by simple copy), the integrity constraints are not managed.
Several methods can be used to manage the integrity constraints in your HFSQL application:
  • Use HAddLink.
  • Perform the automatic modification of the data files when installing the application. The automatic modification of the data files is used to create the integrity constraints on the server.
Importing the structures
The structures of the files found on an existing HFSQL server can be imported into an analysis: on the "Analysis" tab, in the "Creation" group, expand "Import" and select "Import file/table descriptions...".
The management mode of data files may have to be adapted when using an HFSQL Client/Server application. See Differences and limitations specific to an HFSQL Client/Server application for more details.
Minimum version required
  • Version 9
This page is also available for…
Click [Add] to post a comment