PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • Conversion in the data model editor
  • Conversion in the HFSQL Control Center
  • Note
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
Converting a HFSQL Classic database into HFSQL Client/Server
HFSQLHFSQL Client/ServerAvailable only with these kinds of connection
Overview
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 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 into which the current 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. All the files are selected by default but you have the ability to uncheck the ones that must not be converted.
  11. The wizard proposes to copy the data files onto the HFSQL server.
When the operation is ended, the files in HFSQL C/S mode are displayed in yellow in the data model editor.
Conversion in the HFSQL Control Center
To convert a HFSQL Classic database into a HFSQL Client/Server database:
  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).
  4. The import wizard starts.
  5. Specify the directory where your HFSQL Classic 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 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
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
HOpenConnection(ConnectionName)

HChangeConnection("*", ConnectionName)
Minimum required version
  • Version 19
This page is also available for…
Comments
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!

Guenter
Jun. 02 2018