Home | Sign in | French EN

WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WindowsLinuxPHPWEBDEV - Browser code
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Stored procedures
Dynamically changes the connection associated with a data file. The new connection must be known and defined during this change. This new connection will be used during the next opening of the data file.
This allows you to import a description of Oracle tables into the analysis and to use this description to work on data files in HFSQL format. See the detailed examples for more details.
Remark: From version 19, HFSQL is the new name of HyperFileSQL.
// Describe the new connection
HDescribeConnection("MyConnection", "", "", ...
"Server_SQLServer", "dbo", hOledbSQLServer, hOReadWrite, "")
// Establish the new connection
// Specify that "Salaries" is using the new connection
HChangeConnection("Salaries", "MyConnection")
// Start browsing the "Salaries" table on SQLServer
// Close the connection
// Restore the use of connection on Oracle
HChangeConnection("Salaries", "")
// Open the "Salaries" table on Oracle
<Result> = HChangeConnection(<Data file> , <New connection>)
<Result>: Boolean
  • True if the operation was performed,
  • False if a problem occurred. HErrorInfo is used to identify the error.
<Data file>: Character string (with or without quotes)
Name of data file (defined in the analysis) for which the connection must be changed. This data file will be automatically closed in order for its connection to be modified.
If this parameter is set to "*", the process is applied to all known data files, regardless their origin (HFSQL, OLE DB, Native Connector, etc.).
This allows you to transform an HFSQL data file into an OLE DB data file for example.
This parameter can also correspond to the name of a group of files (or custom-folder) defined in the analysis (not available in Android and Android Widget).
<New connection>: Character string (with quotes) or Connection variable
New connection to use. This parameter can correspond to:
  • the name of the connection to a database. This connection was defined in the data model editor or dynamically with HDescribeConnection. If this parameter corresponds to an empty string (""), the initial connection is automatically used.
  • the name of the Connection variable that corresponds to the new connection to use.
  • The connection must be known when running HChangeConnection. If the data file is not known when using HChangeConnection, the connection will be changed during the file declaration.
  • HChangeConnection automatically closes the data file (HClose) whose connection must be modified.
  • HChangeConnection does not open the data file or the connection. The connection defined by HChangeConnection will be used during the next opening of the data file.
Related Examples:
[ + ] This example presents the access to a database via OLE DB with the WLanguage functions.
The following topics are presented in this example:
1/ the independence between your applications and the database
2/ the connection via OLE DB
Summary of the example supplied with WINDEV:
This example explains how to create an application independent of the database used.
The same application with the same source code accesses a HFSQL file or an Access database via OLE DB.
According to this principle, your applications will be able to access all the available databases.
Component : wd260hf.dll
Minimum version required
  • Version 9
This page is also available for…
29 Jul. 2019