DataBind Controls to SQL Server Data in C++Builder

Ready to get started?

Download for a free trial:

Download Now

Learn more:

SQL Server ODBC Driver

Connect to Microsoft SQL Server-compatible databases from any applications that support ODBC connectivity.

The ODBC Driver offers Direct Mode access to SQL Server through standard Java Database Connectivity, providing extensive compatibility with current and legacy MS SQL versions. Supports secure SQL connectivity and authentication via SSL, Kerberos, Integrated Security, etc.



DataBind to SQL Server data in C++Builder with standard components and controls.

The CData ODBC Driver for SQL Server makes it easy to integrate connectivity to live SQL Server data with standard data access components in C++Builder. This article shows how to create a simple visual component library (VCL) application in C++Builder that connects to SQL Server data, executes queries, and displays the results in a grid. An additional section shows how to use FireDAC components to execute commands from code.

Create a FireDAC Connection to SQL Server Data

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Connecting to Microsoft SQL Server

Connect to Microsoft SQL Server using the following properties:

  • Server: The name of the server running SQL Server.
  • User: The username provided for authentication with SQL Server.
  • Password: The password associated with the authenticating user.
  • Database: The name of the SQL Server database.

Connecting to Azure SQL Server and Azure Data Warehouse

You can authenticate to Azure SQL Server or Azure Data Warehouse by setting the following connection properties:

  • Server: The server running Azure. You can find this by logging into the Azure portal and navigating to "SQL databases" (or "SQL data warehouses") -> "Select your database" -> "Overview" -> "Server name."
  • User: The name of the user authenticating to Azure.
  • Password: The password associated with the authenticating user.
  • Database: The name of the database, as seen in the Azure portal on the SQL databases (or SQL warehouses) page.

You can then follow the steps below to use the Data Explorer to create a FireDAC connection to SQL Server.

  1. In a new VCL Forms application, expand the FireDAC node in the Data Explorer.
  2. Right-click the ODBC Data Source node in the Data Explorer.
  3. Click Add New Connection.
  4. Enter a name for the connection.
  5. In the FireDAC Connection Editor that appears, set the DataSource property to the name of the ODBC DSN for SQL Server.

Create VCL Applications with Connectivity to SQL Server Data

Follow the procedure below to start querying SQL Server data from a simple VCL application that displays the results of a query in a grid.

  1. Drop a TFDConnection component onto the form and set the following properties:

    • ConnectionDefName: Select the FireDAC connection to SQL Server.
    • Connected: Select True from the menu and, in the dialog that appears, enter your credentials.
  2. Drop a TFDQuery component onto the form and set the properties below:

    • Connection: Set this property to the TFDConnection component, if this component is not already specified.
    • SQL: Click the button in the SQL property and enter a query. For example:

      SELECT ShipName, Freight FROM Orders
    • Active: Set this property to true.
  3. Drop a TDataSource component onto the form and set the following property:

    • DataSet: In the menu for this property, select the name of the TFDQuery component.
  4. Drop a TDBGrid control onto the form and set the following property:

    • DataSource: Select the name of the TDataSource.
  5. Drop a TFDGUIxWaitCursor onto the form — this is required to avoid a run-time error.

Execute Commands to SQL Server with FireDAC Components

You can use the TFDConnection and TFQuery components to execute queries to SQL Server data. This section provides SQL Server-specific examples of executing queries with the TFQuery component.

Connect to SQL Server Data

To connect to the data source, set the Connected property of the TFDConnection component to true. You can set the same properties from code:

FDConnection1->ConnectionDefName = "CData SQL Server ODBC Source"; FDConnection1->Connected = true;

To connect the TFDQuery component to SQL Server data, set the Connection property of the component. When a TFDQuery component is added at design time, its Connection property is automatically set to point to a TFDConnection on the form, as in the application above.

Create Parameterized Queries

To create a parameterized query, use the following syntax below:

FDQuery1->SQL->Text = "select * from Orders where shipcountry = :ShipCountry"; FDQuery1->ParamByName("shipcountry")->AsString = "USA"; query->Open();

The example above binds a string-type input parameter by name and then opens the dataset that results.

Prepare the Statement

Preparing statements is costly in system resources and time. The connection must be active and open while a statement is prepared. By default, FireDAC prepares the query to avoid recompiling the same query over and over. To disable statement preparation, set ResourceOptions.DirectExecute to True; for example, when you need to execute a query only once.

Execute a Query

To execute a query that returns a result set, such as a select query, use the Open method. The Open method executes the query, returns the result set, and opens it. The Open method will return an error if the query does not produce a result set.

FDQuery1->SQL->Text := "select * from Orders where shipcountry = :ShipCountry"; FDQuery1.ParamByName("shipcountry")->AsString = "USA"; FDQuery1->Open();

To execute a query that does not return a result set, use the ExecSQL method. The ExecSQL method will return an error if the query returns a result set. To retrieve the count of affected rows use the TFD.RowsAffected property.

FDQ.SQL.Text := "delete from Orders where Id = :Id"; FDQuery1->Params->Items[0]->AsString = "x12345"; FDQuery1->ExecSQL(); AnsiString i = FDQuery1->RowsAffected;