Home | Sign in | English UK

  • Overview
  • Conversion in the data model editor
  • Conversion in the HFSQL Control Center
  • Note
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
Converting a HFSQL Classic database into HFSQL Client/Server
HFSQLHFSQL Client/ServerAvailable only with these kinds of connection
To convert a HFSQL Classic database into a HFSQL Client/Server database, WINDEV, WEBDEV and WINDEV Mobile propose two methods:
  • Use the data model editor to directly modify the type of data files: switching from the HFSQL Classic type (data file in a directory) to a HFSQL Client/Server type (connection to a HFSQL server).
  • Use the HFSQL Control Center to directly convert a HFSQL Classic database into HFSQL Client/Server.
Conversion in the data model editor
To convert a HFSQL Classic database into a HFSQL Client/Server database:
  1. Load the project and open the analysis containing the data files to convert.
  2. Select a data file to convert in the data model editor.
  3. Select "Description of data file" from the popup menu.
  4. In the window that is displayed, modify the type of the file: select "HFSQL Client/Server".
  5. The wizard for creating a connection starts.
  6. Enter the name of the HFSQL server or its IP address.
  7. Type the user name and his password (the first time, type "Admin" without password).
  8. Choose or enter the name of the database to which the current data file will be copied.
  9. The connection is created.
  10. The wizard proposes to associate the created connection with other data files found in the analysis. By default, all the data files are selected. You can uncheck those you do not want to convert.
  11. The wizard proposes to copy the data files onto the HFSQL server.
Once the operation is complete, the data files in HFSQL C/S mode appear in yellow in the data model editor.
Conversion in the HFSQL Control Center
  1. Open the HFSQL Control Center.
  2. Connect to an existing HFSQL server ("Admin" user without password by default).
  3. In the top left corner, select "Import a Classic database" from the popup menu of the server (right mouse click).
    Select the server. In the server characteristics pane, in the "Database" group, click "Import an HFSQL Classic database".
  4. The import wizard starts.
  5. Specify the directory where your HFSQL Classic data files are located.
  6. Enter the name of a target database or click the "New" button to create a new database.
  7. Localize the analysis (which means the description of data files to convert). This step is optional but it allows you to retrieve the description of links and integrity rules between data files.
  8. Check the list of data files to convert and start the conversion.
  9. The "Connection code" is used to retrieve, via the clipboard, the code for connecting to the HFSQL Client/Server database. For example:
HDescribeConnection("HyperFileCS", "admin", "<password>", ...
"localhost:4900", "CRMDATABASE", hAccessHFClientServer)
HChangeConnection("*", "HyperFileCS")
Note: The data file names are not modified during the conversion.
Once the database is converted, don't forget to include the connection code in the existing project in order to change the type of connection by programming. For example, the connection code can be copied into the project code.
Example of connection code:
ConnectionName is Connection

// Connection parameters
ConnectionName..Provider = hAccessHFClientServer
ConnectionName..User = "UserName"
ConnectionName..Password = "Password"
ConnectionName..Server = "Myserver:port"
ConnectionName..Database = "MyDatabase"
ConnectionName..CryptMethod = hCryptNo

// Open the connection

HChangeConnection("*", ConnectionName)
Minimum version required
  • Version 19
This page is also available for…
Moving HFSQL Classic to HFSQL C/S using HF Control Center
Warning: when importing HFSQL Classic files to a HFSQL C/S database the files still have to have a .fic extension and the physical file names should be the same as the logical file names!

02 Jun. 2018